List view
- No due date•0/4 issues closed
- Due by October 1, 2025•0/1 issues closed
- Due by October 31, 2025
- Due by December 1, 2025•0/9 issues closed
S-CORE v0.5 is certifiable. This release acts as a baseline for further improvements. Acceptance Criteria: - All S-CORE v0.5 components have all necessary working products according to the S-CORE software development process. - Component Integration Tests are fully available and passed. - Feature Integration Tests are fully available and passed. - Platform Tests are fully available and passed. - Certifiability is demonstrated though an assessment (but no certification is done). - Release and Config Management documents are finished. - All corresponding tools are certified.
Due by December 1, 2025•3/5 issues closed- Due by November 1, 2025•0/1 issues closed
- List of all used tools available
Due by October 1, 2025•0/1 issues closed- Due by October 1, 2025•12/41 issues closed
All components of SCORE v0.5 are available. This contribution request includes all artifacts from requirements to the code including tests. All components are available within the S-CORE infrastructure, adhering to the S-CORE process. Acceptance Criteria: - All feature requests relevant for v0.5 are merged into `score`, including ... - ... Stakeholder Requirements - ... Feature Requirements - The Feature Architecture for every feature exists, including the decomposition into S-CORE modules/components - Component Requirements & Architecture are defined - Component Detailed Design & Implementation & Unit Verification completed - Smoke Integration Test on Development and Production Target - Component and Feature Safety/Security Analyses are done and Feature/Component AoUs are documented - AoUs of the production/ASIL target (OS, Compiler, ...) are defined & respected
Due by October 1, 2025•5/36 issues closedAcceptance Criteria: - Reference hardware and reference OS are defined. - Reference hardware farm is connected to S-CORE CI. - Integration tests on hardware are running periodically (e.g., nightly). - Define hardware relevant integration tests, e.g. performance, and corresponding KPIs
Due by October 1, 2025•0/2 issues closedAcceptance Criteria: - scope for Release v1.0 is defined in Software Architecture community and agreed with TL/PL-circle. - Feature requests for missing Release v1.0 modules are created and agreed. - POCs are done to show possible implementation approach
Due by August 1, 2025•2/13 issues closedAcceptance Criteria: - All processes are defined. - Samples are available. - Maturity Level: Managed
Due by September 1, 2025•14/31 issues closedDefine demo use-cases (aka. Eclipse SDV Blueprints) in which we plan to use our Release v0.5 modules (e.g., a real vehicle) to prove its usability (performance, scaling, ...). Consider SDV Blueprints, SDV Hackathons, Autoware etc.
Overdue by 1 month(s)•Due by June 1, 2025The features of the S-CORE v0.5 MVP are according to the S-CORE processes and all artefacts (apart from integration tests and safety artefacts) are created initially. Acceptance Criteria: - All necessary artifacts (requirements, unit tests, architecture) exist in S-CORE format and are generated/executed in CI pipeline for the Release v0.5 components
Overdue by 1 month(s)•Due by June 1, 2025Acceptance Criteria: - Reference QEMU image containing (armv8/aarch64 & QNX 8) is available - There are integration tests available which run on the image. - Image is built and tested as part of automated CI/CD pipeline. - S-CORE v0.5 Feature Complete is integrated in image: - daemon components (if existing) are deployed to the image - library components (if existing) are available to link/compile Prerequisites: - https://github.com/eclipse-score/score/milestone/9 - https://github.com/eclipse-score/score/milestone/12
Due by August 1, 2025•1/18 issues closedThe project supports the QNX toolchain. Acceptance Criteria: - The existing modules can be built with qcc. Prerequisites: - QNX Version and license defined
Overdue by 6 day(s)•Due by July 15, 2025•0/8 issues closedFor all existing solutions for Release v0.5 analysis of missing features (GAP analysis) is finished, POCs has confirmed possible implementation solutions and everything is documented in Feature Requests. Feature Requests are confirmed in the TL round and Software Architecture community, tickets are created and prioritized for implementation accrodingly
Overdue by 20 day(s)•Due by July 1, 2025•14/42 issues closedTesting strategy is defined and corresponding tooling is implemented. Acceptance Criteria: - Process and Tooling for Testing (e.g., component or integration tests) are available.
Due by August 1, 2025•27/38 issues closedAcceptance Criteria: - Reference QEMU (or OCI Container?) image containing x86_64 (TODO: armv8/aarch64 relevant?) & Linux (TODO: Ubuntu 24.04?) is available - There are integration tests available which run on the image. - Image is built and tested as part of automated CI/CD pipeline. - S-CORE v0.5 Feature Complete is integrated in image: - daemon components (if existing) are deployed to the image - library components (if existing) are available to link/compile Prerequisites: - https://github.com/eclipse-score/score/milestone/7 - https://github.com/eclipse-score/score/milestone/8
Overdue by 20 day(s)•Due by July 1, 2025•1/7 issues closedAll MVP defined features (FEO, IPC, Logging, Common Libraries, Persistency) can be built in software module repositiories. Until then, the modules are handled within the incubation repositories. Acceptance Criteria: - All modules use a common repository template (build, CI, gitlint, README, ...); to be checked by operational whether Git submodule/bazel module can be used to avoid code duplication. - All modules are built with bazel, (C++17: clang for x86 Linux with -Wall, -Wextra, -pedantic; Rust: rustc 1.83.0). - Unit tests are built and run, also via GitHub Actions. - No strict adherence to coding guidelines, but coding guidelines are available. - How to guide for reference build & test environment. - Result: every software module can be built inside of its repository. No common integration so far, no running image. Prerequisites: Process & Tools Enable Development https://github.com/eclipse-score/score/milestone/7 mostly done
Overdue by 1 month(s)•Due by June 2, 2025•12/13 issues closedLeft side of V-Model done. Acceptance Criteria: - Process & Tooling for requirements & architecture is available (sphinx-needs incl. additional checks for verifying traceability/consistency). - Process & Tooling for Detailed design, implementation & unit verification defined and implemented (e.g. spinx-test-reports). - CI/CD is capable to automatically verify the consistency & traceability. - Tooling for test coverage & static code analysis. Prerequisites: Selection of tooling (e.g. static code analysis).
Due by August 1, 2025•31/65 issues closedJust testing. See #450
Overdue by 3 month(s)•Due by March 31, 2025•16/17 issues closed- Overdue by 4 month(s)•Due by March 18, 2025•19/19 issues closed
SCORE v0.5 is certifiable. This is the first version fulfilling the required KPIs for the certification. This release acts as a baseline for further improvements.
Due by December 1, 2025•0/1 issues closedAll components of v0.5 are implemented in incubation repository. The SCORE Architecture Community has reached consensus about the technical concepts behind the components. At this stage, no process and infrastructure adherence are required. The intention is keep the entry barrier as low as possible for existing contributions to reach consensus on a code basis.
Overdue by 3 month(s)•Due by March 30, 2025•1/1 issues closed