Prepare the roadmap for v0.8-v1.0

[lavrovvalera]

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]

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.6.0) and connecting to it...
INFO: Invocation ID: 31e57724-dc8a-4124-aefb-d4a3bcb6c7b3
Computing main repo mapping: 
WARNING: /home/runner/work/time/time/MODULE.bazel:13:7: The attribute 'compatibility_level' in module() is a no-op and will be removed in a future Bazel release. Please remove it from your MODULE.bazel file.
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 3 packages loaded
Loading: 3 packages loaded
    currently loading: 
Loading: 3 packages loaded
    currently loading: 
Loading: 3 packages loaded
    currently loading: 
Loading: 3 packages loaded
    currently loading: 
Loading: 3 packages loaded
    currently loading: 
Analyzing: target //:license-check (4 packages loaded, 0 targets configured)
Analyzing: target //:license-check (4 packages loaded, 0 targets configured)

Analyzing: target //:license-check (31 packages loaded, 10 targets configured)

Analyzing: target //:license-check (88 packages loaded, 10 targets configured)

Analyzing: target //:license-check (143 packages loaded, 2933 targets configured)

Analyzing: target //:license-check (153 packages loaded, 6325 targets configured)

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

Analyzing: target //:license-check (164 packages loaded, 9276 targets configured)

Analyzing: target //:license-check (165 packages loaded, 9284 targets configured)

Analyzing: target //:license-check (165 packages loaded, 9284 targets configured)

Analyzing: target //:license-check (165 packages loaded, 9284 targets configured)

Analyzing: target //:license-check (168 packages loaded, 11172 targets configured)

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

INFO: Analyzed target //:license-check (170 packages loaded, 11422 targets configured).
[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] JavaToolchainCompileBootClasspath external/rules_java+/toolchains/platformclasspath.jar; 0s disk-cache, processwrapper-sandbox
[15 / 16] Building license.check.license_check.jar (); 0s disk-cache, multiplex-worker
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: 29.636s, Critical Path: 2.53s
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]

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

[BjoernAtBosch]

Basically looks good. Two comments:

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

[BjoernAtBosch]

Here and everywhere: Replace inc_time by time

[BjoernAtBosch]

Suggested change

	The table below compares what the **project roadmap requires** at each gate against what the
	Time module can **realistically deliver** given the v0.8 baseline state.
	The table below compares what the **project roadmap requires** ("target") at each gate against what the
	Time module can **realistically deliver** ("expected delivery") given the v0.8 baseline state.

[BjoernAtBosch]

Suggested change

	The table below compares what the **project roadmap requires** at each gate against what the
	Time module can **realistically deliver** given the v0.8 baseline state.
	The table below compares what the **project roadmap requires** ("target") at each gate against what the
	Time module can **realistically deliver** ("expected delivery") given the v0.8 baseline state.