[Proposal] Concrete actions towards v0.5 release

[antonkri]

1. Let us concentrate for now only on C++ implementation and its qualification. RUST topic should be postponed, we can proceed with it later, as soon as C/C++ is in a good shape. The only RUST topic we should follow in parallel to C/C++ topic is getting qualified RUST compiler and std lib.

   • Who will follow up/be responsible for clarifying topics regarding qualified RUST compiler and std lib to the project?

2. As following C++ implementations (IPC (LoLa), Logging, Base Libs, Persistency) were integrated into the project, we need first to ensure, that we make use of what we have and bring things, that we already have to the end. Following working packages might make sense:

   • Buildable and runnable

     • Can all the components be built with gcc toolchain? Do we have an established CI pipeline, that ensures, that the build is not broken? -> Nikola Radakovic, Alex Lanin, Jochen Hönle
     • Can all the components be built with qcc toolchain? Do we have an established CI pipeline, that ensures, that the build is not broken? (task for corresponding FTs) -> Lukasz/Nikola, Task for every FT.
     • Do we have a corresponding (QNX: prio 1, Linux: prio 2) image in the reference integration repository with a demo, that can be downloaded and executed by everyone? -> New Feature Team: Release & Integration (Lukasz, ...).
       • IPC (LoLa) does already have number of test applications for testing, as LoLa is itself only a library. LoLa is already make use of Logging and BaseLibs. Should we start with these applications and extend later with persistency? -> Release & Integration together Communication FT.

   • Unit-tests & Detailed Design

     • Can we already execute all unit-tests with gcc toolchain? Do we have an established CI pipeline, that ensures, that the tests are not broken? -> check with Alexander Lanin/Nikola Radakovic/Piotr
     • Where is unit-test coverage reported? We need eventually a nightly test build and reporting of coverage results at official location -> Piotr, Nikola Radakovic, Alexander Lanin
     • Ideally, we agree how to specify detailed design and can link detailed design to unit-tests to source-code -> Jochen/Alexander Lanin.

   • ITF Tests

     • ITF framework was initially integrated, we could right integration tests to test feature requirements.
     • Logging/LoLa has already ITF tests, we should make them run with the version of ITF framework, that was introduced to S-CORE (task for corresponding FTs) -> Communication FT with Dragan/Piotr should try to run first ITF Tests.
     • Establish a pipeline to ensure ITF tests are always green -> Piotr/Alexander Lanin
     • Agree on how to link ITF test to feature requirements and generate feature requirements coverage. -> Jochen/Alexander/Schemmel/Schu.
     • Process Pilot for right side of V.

   • Documentation

     • Step-by-step developer documentation, that explains what we can already do in S-CORE and instructions how to do this, starting with working packages above -> Alexander Schemmel/Markus Schu.

   • Multi-repo

     • Multirepo concept should be reworked and implemented. -> Anton K/ Jochen / Alexander Lanin

   • Platform Safety manager

     • name platform safety manager

[antonkri]

2025-08-05

Participants

@antonkri
@johannes-esr
@FScholPer

Meeting Minutes & Agenda

• Review of planning proposal: https://github.com/orgs/eclipse-score/projects/26/views/4