You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This document provides an overview of the changes, improvements, and bug fixes included in the software platform release version v0.7.0 as compared to the platform’s origin release (v0.6).
35
+
34
36
The SCORE 0.7 platform release centers on safety formalization (vulnerability management, OS tier definitions, safety manuals), Rust interoperability (FFI bindings in baselibs and a full Rust COM API in communication),
35
37
and infrastructure hardening (toolchain improvements, Dependabot, CodeQL).
36
38
39
+
Disclaimer
40
+
----------
41
+
42
+
This release note does not "release for production", as it does not come with a safety argumentation and a performed safety assessment.
43
+
The work products compiled in the safety package are created with care according to a process satisfying standards, but the as the project,
44
+
being a non-profit and open source organization, can not take over any liability for its content.
45
+
46
+
Changes to the Platform
47
+
^^^^^^^^^^^^^^^^^^^^^^^
48
+
49
+
New Features
50
+
------------
51
+
52
+
No new features were added in this release.
53
+
54
+
Improvements
55
+
------------
56
+
37
57
The release significantly expanded integration testing capabilities, with ITF upgrade and test execution now supported on both Docker and QNX targets using the new py_itf_test Bazel rule.
38
58
The CI/CD pipeline was overhauled — the bash-based integration script was replaced with Python and the pipeline became more robust with improved build caching, automatic cancellation of superseded runs, and workflow steps pinned to exact commit SHAs for supply-chain safety.
39
59
EBcLfSA integration was updated to the new structure and extended with Rust application support.
40
60
On the documentation side, the build pipeline was fixed and an integration status dashboard was introduced to provide visibility into module health across the platform.
41
61
Infrastructure-wise, Bzlmod lockfile consistency is now enforced in CI, the AutoSD image version is frozen for reproducible builds, and image filesystem rules were migrated to the new Bazel API.
42
62
63
+
43
64
Eclipse S-CORE book
44
65
-------------------
66
+
45
67
The `Eclipse S-CORE book <https://eclipse-score.github.io/score/main/handbook/index.html>`_
46
68
is a “how-to” guide for users getting started with the project or who want to contribute new modules.
Kyron is a customizable, high-performance async/await runtime designed for advanced concurrent programming with focus on functional safety.
110
135
It allows fine-grained control over scheduling, thread management, and workload isolation through configurable execution engines.
111
136
@@ -114,15 +139,17 @@ It allows fine-grained control over scheduling, thread management, and workload
114
139
115
140
116
141
Lifecycle & Health Management
117
-
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
142
+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
143
+
118
144
Lifecycle module provides a Launch Manager for process lifecycle management as well as a Health Monitoring library to support supervision of process behavior.
Test scenarios provide a backend for defining C++ and Rust implemented test scenarios that allow parametrized execution of built scenario applications which are the input for test cases.
- Increase to newest bazel registry versions: https://eclipse-score.github.io/bazel_registry_ui
203
247
- Versions can be found under: https://github.com/eclipse-score/reference_integration/blob/v0.7.0/known_good.json
204
248
249
+
Upgrade Instructions
250
+
^^^^^^^^^^^^^^^^^^^^
251
+
252
+
Not evaluated yet, but expected to be straightforward as no breaking changes are introduced in this release. Please refer to the release notes of the individual modules for any specific upgrade instructions.
253
+
205
254
Contact Information
206
-
----------------------
255
+
-------------------
256
+
207
257
For any questions or support, please contact the *Project leads* or raise an issue/discussion.
This is the content according to the template (see :need:`doc__platform_verification_report`) for the platform verification report, filled in with the information available for this release.
27
+
28
+
1. Verification Coverage
29
+
-------------------------
30
+
31
+
1.1. Requirements
32
+
~~~~~~~~~~~~~~~~~
33
+
34
+
For this release, the requirements-related verification output is as follows:
35
+
36
+
* Lists of stakeholder and feature requirements tested (split in separate lists for QM and ASIL) by which test case, passed/failed/not_run and completeness verdict:
37
+
No release-specific requirement verification matrix is available in this platform verification report.
38
+
39
+
* List of external component Assumptions of Use and coverage by platform safety manual:
40
+
Assumptions of Use requirements and safety manual content exist in the documentation set, but no release-specific coverage matrix is provided in this platform verification report.
41
+
42
+
* List of stakeholder requirements (ASIL rated) linked to inspection checklist and verdict derived from PR export:
43
+
No PR-export-derived stakeholder requirement inspection list is available in this repository for this release.
44
+
45
+
1.2. Architecture
46
+
~~~~~~~~~~~~~~~~~
47
+
48
+
For this release, the architecture-related verification output is as follows:
49
+
50
+
* List of feature architecture tags (split into separate lists for QM and ASIL) tested by test case or other verification method:
51
+
No release-specific architecture-tag verification matrix is available in this platform verification report.
52
+
53
+
* List of feature architecture tags (ASIL rated) linked to inspection checklist and verdict derived from PR export:
54
+
Architecture inspection checklists exist in the documentation set for individual modules and features, but no release-specific PR-export-derived list is available in this repository for this release.
55
+
56
+
2. Safety Analyses Report
57
+
-------------------------
58
+
59
+
For this release, the safety-analyses-related verification output is as follows:
60
+
61
+
* List of the performed Platform and Feature Safety Analyses:
62
+
No release-specific consolidated list of performed platform-level and feature-level safety analyses is available in this platform verification report.
63
+
64
+
* Pass/fail result and open mitigations for each safety analysis:
65
+
No release-specific result table for safety analyses, including open mitigations, is provided in this report.
66
+
67
+
68
+
3. Test results
69
+
---------------
70
+
71
+
Test result per test case with status passed/failed/not_run for :need:`wp__verification_platform_int_test` and :need:`wp__verification_feat_int_test`.
72
+
73
+
For this release, detailed per-test-case results are not available in this report yet.
74
+
The following referenced summary pages exist only.
75
+
76
+
.. toctree::
77
+
:titlesonly:
78
+
79
+
Unit Tests Summary <unit_test_summary>
80
+
Coverage Analysis Summary <coverage_summary>
81
+
82
+
83
+
4. Test logs
84
+
---------------
85
+
86
+
Link to test log per test case for :need:`wp__verification_platform_int_test` and :need:`wp__verification_feat_int_test`.
87
+
88
+
For this release, detailed test logs are not available in this report yet.
0 commit comments