Skip to content

Prepare the roadmap for v0.8-v1.0 - #100

Open
lavrovvalera wants to merge 1 commit into
eclipse-score:mainfrom
lavrovvalera:vala_time_roadmap
Open

Prepare the roadmap for v0.8-v1.0#100
lavrovvalera wants to merge 1 commit into
eclipse-score:mainfrom
lavrovvalera:vala_time_roadmap

Conversation

@lavrovvalera

Copy link
Copy Markdown
Contributor

Add Draft Time Module Roadmap to S-CORE v1.0

Closes #99

Summary

Adds an initial delivery plan for the Time module on the path from v0.8 to S-CORE v1.0.
The plan documents agreed maturity-level targets (L0–L4) per process area and per SW component
at each release gate, making gaps and risks explicit so the team can plan sprint work accordingly.

Changes

  • docs/release/roadmap.rst — new document covering:
    • Feature scope for v1.0 (SteadyTime, SystemTime, VehicleTime, HighResSteadyTime in-scope; AbsoluteTime deferred)
    • Roadmap Overview table: artefact × milestone with L0–L4 targets for all process areas (PA2–PA6)
    • Detailed Breakdown: per-component tables for score/time, score/time_daemon, score/time_slave, score/ts_client
    • Known constraints documented: score/time_slave one-milestone lag, score/ts_client dependency on PR Replace mmap-based IPC with score_baselibs SharedMemoryFactory in ts_client #54
    • Summary gate compliance table (project requirement vs. Time module delivery + gap/risk)
    • Epics & tracking links to the TIM board
  • docs/index.rst — adds a "Release Planning" toctree section pointing to the new document
  • proposed_tickets.md — records proposed GitHub issues for the v0.9–v1.0 backlog (reference only; not part of the rendered docs)

Notes

  • This is a living document — targets will be updated as work progresses through each release gate
  • The time_module_roadmap.md at the repository root is superseded by this RST file and can be removed in a follow-up cleanup

@github-actions

github-actions Bot commented Jun 23, 2026

Copy link
Copy Markdown

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run //:license-check

Status: ⚠️ Needs Review

Click to expand output
[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.3.0) and connecting to it...
INFO: Invocation ID: 1824ca3d-ee16-4b69-bd29-396e9365220e
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
WARNING: For repository 'aspect_rules_lint', the root module requires module version aspect_rules_lint@1.5.3, but got aspect_rules_lint@2.0.0 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
Computing main repo mapping: 
Loading: 
Loading: 2 packages loaded
Loading: 2 packages loaded
    currently loading: 
Loading: 2 packages loaded
    currently loading: 
Loading: 2 packages loaded
    currently loading: 
Loading: 2 packages loaded
    currently loading: 
Loading: 2 packages loaded
    currently loading: 
Analyzing: target //:license-check (3 packages loaded, 0 targets configured)
Analyzing: target //:license-check (3 packages loaded, 0 targets configured)

Analyzing: target //:license-check (71 packages loaded, 9 targets configured)

Analyzing: target //:license-check (124 packages loaded, 214 targets configured)

Analyzing: target //:license-check (157 packages loaded, 3335 targets configured)

Analyzing: target //:license-check (158 packages loaded, 7970 targets configured)

Analyzing: target //:license-check (169 packages loaded, 8049 targets configured)

Analyzing: target //:license-check (169 packages loaded, 8049 targets configured)

Analyzing: target //:license-check (169 packages loaded, 8049 targets configured)

Analyzing: target //:license-check (169 packages loaded, 8049 targets configured)

Analyzing: target //:license-check (173 packages loaded, 10058 targets configured)

Analyzing: target //:license-check (173 packages loaded, 10058 targets configured)

INFO: Analyzed target //:license-check (174 packages loaded, 10184 targets configured).
[9 / 16] [Prepa] Expanding template external/score_tooling+/dash/tool/formatters/dash_format_converter [for tool]
[12 / 16] JavaToolchainCompileClasses external/rules_java+/toolchains/platformclasspath_classes; 0s disk-cache, processwrapper-sandbox ... (2 actions running)
INFO: From Generating Dash formatted dependency file ...:
INFO: Successfully converted 2 packages from Cargo.lock to bazel-out/k8-fastbuild/bin/formatted.txt
[14 / 16] checking cached actions
[14 / 16] JavaToolchainCompileBootClasspath external/rules_java+/toolchains/platformclasspath.jar; 0s disk-cache, processwrapper-sandbox
INFO: Found 1 target...
Target //:license.check.license_check up-to-date:
  bazel-bin/license.check.license_check
  bazel-bin/license.check.license_check.jar
INFO: Elapsed time: 41.386s, Critical Path: 2.50s
INFO: 16 processes: 12 internal, 3 processwrapper-sandbox, 1 worker.
INFO: Build completed successfully, 16 total actions
INFO: Running command line: bazel-bin/license.check.license_check ./formatted.txt <args omitted>
usage: org.eclipse.dash.licenses.cli.Main [-batch <int>] [-cd <url>]
       [-confidence <int>] [-ef <url>] [-excludeSources <sources>] [-help] [-lic
       <url>] [-project <shortname>] [-repo <url>] [-review] [-summary <file>]
       [-timeout <seconds>] [-token <token>]

@github-actions

Copy link
Copy Markdown

The created documentation from the pull request is available at: docu-html

@BjoernAtBosch BjoernAtBosch left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Basically looks good. Two comments:

  • Is the state still up-to-date?
  • Duplication of the roadmap - see comment to md file

Comment thread time_module_roadmap.md

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems to be a duplicate of the rst file above, largely.
I'd prefer not to do this because of danger, that both files get out of sync over time and require additional maintenance efforts.
Is there a way to generate one of both from the other?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

Define Draft Time Module Roadmap to S-CORE v1.0

3 participants