Scope v0.5 Beta release preparation #2219
Description
Following activities should be done as preparation for release S-CORE v0.5 Beta (Due Date: 18.12.2025)
General
- Prepare release description: S-CORE v0.5 beta release notes #2300
- Align internally and describe in the release notes what we mean with "certifiable" and how far we go with 0.5
- Align release plan for 0.5
- This time by release description invest more time in providing more links and description for the processes, e.g. release process
- Rework meta-model and enable tooling for the new version if the meta-model
- Pilot of the unified Toolchain -> @nradakovic
Persistency
- Fix unit testing with current gcc toolchain
Every module
- Move component requirements/architecture and AoUs to module repository (is this one still valid) -> only baselibs
- Update doc-as-code version to 2.2.0
- Usage of Toolchain gcc 0.0.5 tag
- Ensure ALL targets can be compiled with Linux toolchain for x86/(arm). This check should be part of module release workflow.
- Ensure ALL targets can be compiled with QNX toolchain for x86/(arm). This check should be part of module release workflow.
- Ensure ALL unit-test targets (Linux host) can be successfully executed. This check should be part of module release workflow.
- [C++ modules only] Ensure unit-test coverage is measurable (gcov)
- Create a release containing meaningful release notes and publish it to the bazel registry
- Provide more detailed description of the release in the overall release notes: S-CORE v0.5 beta release notes #2300
Reference integration
- Extend test_integration workflow with qcc compilation for all C++ components
- Extend test_integration workflow with unit-test execution and unit-test coverage report for all C++ components
- Provide downloadable images for EB, RedHat Linux and QNX for Qemu.
- Provide downloadable Image for Raspberry Pi
Safety
- Prepare safety analysis for baselibs and communication
Sub-issues
Metadata
Metadata
Assignees
Projects
Status