From 523ff63b7015ef92ff86002bda50969079336196 Mon Sep 17 00:00:00 2001 From: Anton Krivoborodov Date: Fri, 5 Dec 2025 16:31:45 +0100 Subject: [PATCH 01/25] Add template for v0.5 beta release --- docs/score_releases/score_releases/index.rst | 1 + .../score_releases/score_v0_5_alpha.rst | 2 +- .../score_releases/score_v0_5_beta.rst | 139 ++++++++++++++++++ 3 files changed, 141 insertions(+), 1 deletion(-) create mode 100644 docs/score_releases/score_releases/score_v0_5_beta.rst diff --git a/docs/score_releases/score_releases/index.rst b/docs/score_releases/score_releases/index.rst index af5ec410fd5..69e7290bb87 100644 --- a/docs/score_releases/score_releases/index.rst +++ b/docs/score_releases/score_releases/index.rst @@ -6,3 +6,4 @@ S-CORE Releases :maxdepth: 1 score_v0_5_alpha.rst + score_v0_5_beta.rst diff --git a/docs/score_releases/score_releases/score_v0_5_alpha.rst b/docs/score_releases/score_releases/score_v0_5_alpha.rst index 88b0f2c4aa8..e3a5d950641 100644 --- a/docs/score_releases/score_releases/score_v0_5_alpha.rst +++ b/docs/score_releases/score_releases/score_v0_5_alpha.rst @@ -17,7 +17,7 @@ S-Core v0.5-alpha release notes .. document:: S-Core v0.5-alpha release note :id: doc__score_v05_alpha_release_note - :status: draft + :status: valid :safety: ASIL_B :security: YES :realizes: wp__platform_sw_release_note diff --git a/docs/score_releases/score_releases/score_v0_5_beta.rst b/docs/score_releases/score_releases/score_v0_5_beta.rst new file mode 100644 index 00000000000..2dae400e50f --- /dev/null +++ b/docs/score_releases/score_releases/score_v0_5_beta.rst @@ -0,0 +1,139 @@ +.. + # ******************************************************************************* + # Copyright (c) 2025 Contributors to the Eclipse Foundation + # + # See the NOTICE file(s) distributed with this work for additional + # information regarding copyright ownership. + # + # This program and the accompanying materials are made available under the + # terms of the Apache License Version 2.0 which is available at + # https://www.apache.org/licenses/LICENSE-2.0 + # + # SPDX-License-Identifier: Apache-2.0 + # ******************************************************************************* + +S-Core v0.5-beta release notes +=============================== + +.. document:: S-Core v0.5-beta release note + :id: doc__score_v05_beta_release_note + :status: draft + :safety: ASIL_B + :security: YES + :realizes: wp__platform_sw_release_note + +| **Platform Name**: S-CORE +| **Release Tag**: v0.5.0-beta +| **Origin Release Tag**: none - first published release +| **Release Date**: 2025-12-18 + +Overview +^^^^^^^^^ +TBD + +| + +Highlights +----------- +TBD + +Timeline +--------- +TBD + +| + +For a detailed and always up-to-date planning view, see the `GitHub project `_. + +Eclipse S-CORE book +------------------- +TBD + +Improvements +^^^^^^^^^^^^^ +TBD + +Bug Fixes +^^^^^^^^^^^^ +TBD + +Integrated Software Modules +----------------------------- + +Communication +~~~~~~~~~~~~~ +TBD + +Fixed Execution Order Framework(FEO) +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +TBD + +Baselibs +~~~~~~~~~~~~~ +TBD + + +Persistency +~~~~~~~~~~~~~ +TBD + + +Orchestrator (Kyron and orchestration framework) +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +TBD + + +Reference integration +~~~~~~~~~~~~~~~~~~~~~~ +TBD + +Reference QNX image ++++++++++++++++++++++ +TBD + +Reference Red Hat AutoSD Linux image (Experimental) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +TBD + +Reference Elektrobit corbos Linux for Safety Applications Linux image (Experimental) +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +TBD + +Associated Infrastructure Modules +----------------------------------- + +process_description +~~~~~~~~~~~~~~~~~~~~~~~ +TBD + +docs-as-code +~~~~~~~~~~~~~~ +TBD + +tooling +~~~~~~~~~~~~~~ +TBD + +ITF (Integration Testing Framework) +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +TBD + +Test Scenarios +~~~~~~~~~~~~~~~ +TBD + +Performed Verification +---------------------- +TBD + +Known Issues +---------------------- +- see release notes of every module seperately + +Upgrade Instructions +---------------------- +- TBD + +Contact Information +---------------------- +For any questions or support, please contact the *Project lead* or raise an issue/discussion. From ea910cd5e297a6e6108a989ecbc4b8af57402aef Mon Sep 17 00:00:00 2001 From: Frank Scholter Peres Date: Fri, 12 Dec 2025 09:36:36 +0000 Subject: [PATCH 02/25] fix: handbook --- docs/handbook/own_application/index.rst | 35 ++++++++++++++++--------- 1 file changed, 22 insertions(+), 13 deletions(-) diff --git a/docs/handbook/own_application/index.rst b/docs/handbook/own_application/index.rst index edfea1b76e0..3d7c0ba787c 100644 --- a/docs/handbook/own_application/index.rst +++ b/docs/handbook/own_application/index.rst @@ -33,7 +33,7 @@ To integrate the communication module into your project, follow these steps: 1. Setup ----------- -Start by creating a new project in your preferred IDE (e.g., Visual Studio Code). A ready-to-use devcontainer is available under: +Start by creating a new project in your preferred IDE (e.g., Visual Studio Code). A ready-to-use devcontainer is available under: - https://github.com/eclipse-score/devcontainer @@ -54,7 +54,7 @@ Reference documentation for the communication module: module(name = "use_com_test") - bazel_dep(name = "score_toolchains_gcc", version = "0.4", dev_dependency=True) + bazel_dep(name = "score_toolchains_gcc", version = "0.5", dev_dependency=True) gcc = use_extension("@score_toolchains_gcc//extensions:gcc.bzl", "gcc", dev_dependency=True) gcc.toolchain( @@ -84,8 +84,16 @@ Reference documentation for the communication module: ) bazel_dep(name = "boost.program_options", version = "1.87.0") - bazel_dep(name = "score-baselibs", version = "0.1.3") - bazel_dep(name = "communication", version = "0.1.1") + bazel_dep(name = "score_baselibs", version = "0.1.3") + bazel_dep(name = "score_communication", version = "0.1.1") + + # TRLC dependency for requirements traceability + bazel_dep(name = "trlc", version = "0.0.0") + git_override( + module_name = "trlc", + commit = "ede35c4411d41abe42b8f19e78f8989ff79ad3d8", + remote = "https://github.com/bmw-software-engineering/trlc.git", + ) Be aware that the version numbers change over time. Always check the latest versions in the respective bazel registry @@ -108,7 +116,8 @@ Be aware that the version numbers change over time. Always check the latest vers common --@score-baselibs//score/json:base_library=nlohmann common --@communication//score/mw/com/flags:tracing_library=stub - common --registry=https://raw.githubusercontent.com/eclipse-score/bazel_registry/refs/heads/main/ + common --registry=https://raw.githubusercontent.com/eclipse-score/bazel_registry/v0.5.0-alpha/ + common --registry=https://bcr.bazel.build ^^^^^^^^^^^^^ @@ -116,14 +125,14 @@ Be aware that the version numbers change over time. Always check the latest vers ^^^^^^^^^^^^^ If you start with an empty project, add an empty file named ``BUILD`` into your project root. -Now you can now run build the project with the command bazel ``bazel build //...`` +Now you can now run build the project with the command bazel ``bazel build //...`` (At this point nothing happens yet, because no targets are defined). You can now either continue with this guide to create a minimal consumer-producer example or start coding your own application ------------ -2. Use it :) +1. Use it :) ------------ Once your project is set up, you can start sending and receiving messages. @@ -133,9 +142,9 @@ Once your project is set up, you can start sending and receiving messages. ^^^^^^^^^^^^^^^^^^^^ Create a folder named ``src`` in your root project directory. -Inside ``src``, create the following folders: +Inside ``src``, create the following folders: -- ``consumer`` +- ``consumer`` - ``producer`` additional folders if needed. @@ -278,11 +287,11 @@ After that, create the file ``producer.cpp``. The constructor initializes the communication skeleton ``create_result``. -``RunProducer``: +``RunProducer``: - checks if the initialization of ``create_result`` was successful -- offers service -- enters a loop and sends our messages +- offers service +- enters a loop and sends our messages - stops offering the service at the end @@ -298,4 +307,4 @@ Navigate to the ``consumer`` directory and create a new file called ``consumer.h ^^^^^^^^^^^^^^ For a complete example implementation, see the example folder -https://github.com/eclipse-score/communication/tree/main/score/mw/com/example/ipc_bridge \ No newline at end of file +https://github.com/eclipse-score/communication/tree/main/score/mw/com/example/ipc_bridge From 76db9ec619f647c576929b7d53384599196e0912 Mon Sep 17 00:00:00 2001 From: Frank Scholter Peres Date: Fri, 12 Dec 2025 13:07:58 +0000 Subject: [PATCH 03/25] added code_of_conduct and fixed contribution guidelines --- CODE_OF_CONDUCT.md | 93 ++++++++++++++++++++++++++++++++++++++++++++++ CONTRIBUTION.md | 44 +++++++++++++++++----- 2 files changed, 128 insertions(+), 9 deletions(-) create mode 100644 CODE_OF_CONDUCT.md diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 00000000000..faa735b35e4 --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,93 @@ +# Community Code of Conduct + +**Version 2.0 +January 1, 2023** + +## Our Pledge + +In the interest of fostering an open and welcoming environment, we as community members, contributors, Committers[^1], and Project Leads (collectively "Contributors") pledge to make participation in our projects and our community a harassment-free and inclusive experience for everyone. + +This Community Code of Conduct ("Code") outlines our behavior expectations as members of our community in all Eclipse Foundation activities, both offline and online. It is not intended to govern scenarios or behaviors outside of the scope of Eclipse Foundation activities. Nor is it intended to replace or supersede the protections offered to all our community members under the law. Please follow both the spirit and letter of this Code and encourage other Contributors to follow these principles into our work. Failure to read or acknowledge this Code does not excuse a Contributor from compliance with the Code. + +## Our Standards + +Examples of behavior that contribute to creating a positive and professional environment include: + +- Using welcoming and inclusive language; +- Actively encouraging all voices; +- Helping others bring their perspectives and listening actively. If you find yourself dominating a discussion, it is especially important to encourage other voices to join in; +- Being respectful of differing viewpoints and experiences; +- Gracefully accepting constructive criticism; +- Focusing on what is best for the community; +- Showing empathy towards other community members; +- Being direct but professional; and +- Leading by example by holding yourself and others accountable + +Examples of unacceptable behavior by Contributors include: + +- The use of sexualized language or imagery; +- Unwelcome sexual attention or advances; +- Trolling, insulting/derogatory comments, and personal or political attacks; +- Public or private harassment, repeated harassment; +- Publishing others' private information, such as a physical or electronic address, without explicit permission; +- Violent threats or language directed against another person; +- Sexist, racist, or otherwise discriminatory jokes and language; +- Posting sexually explicit or violent material; +- Sharing private content, such as emails sent privately or non-publicly, or unlogged forums such as IRC channel history; +- Personal insults, especially those using racist or sexist terms; +- Excessive or unnecessary profanity; +- Advocating for, or encouraging, any of the above behavior; and +- Other conduct which could reasonably be considered inappropriate in a professional setting + +## Our Responsibilities + +With the support of the Eclipse Foundation employees, consultants, officers, and directors (collectively, the "Staff"), Committers, and Project Leads, the Eclipse Foundation Conduct Committee (the "Conduct Committee") is responsible for clarifying the standards of acceptable behavior. The Conduct Committee takes appropriate and fair corrective action in response to any instances of unacceptable behavior. + +## Scope + +This Code applies within all Project, Working Group, and Interest Group spaces and communication channels of the Eclipse Foundation (collectively, "Eclipse spaces"), within any Eclipse-organized event or meeting, and in public spaces when an individual is representing an Eclipse Foundation Project, Working Group, Interest Group, or their communities. Examples of representing a Project or community include posting via an official social media account, personal accounts, or acting as an appointed representative at an online or offline event. Representation of Projects, Working Groups, and Interest Groups may be further defined and clarified by Committers, Project Leads, or the Staff. + +## Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the Conduct Committee via conduct@eclipse-foundation.org. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. Without the explicit consent of the reporter, the Conduct Committee is obligated to maintain confidentiality with regard to the reporter of an incident. The Conduct Committee is further obligated to ensure that the respondent is provided with sufficient information about the complaint to reply. If such details cannot be provided while maintaining confidentiality, the Conduct Committee will take the respondent‘s inability to provide a defense into account in its deliberations and decisions. Further details of enforcement guidelines may be posted separately. + +Staff, Committers and Project Leads have the right to report, remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code, or to block temporarily or permanently any Contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. Any such actions will be reported to the Conduct Committee for transparency and record keeping. + +Any Staff (including officers and directors of the Eclipse Foundation), Committers, Project Leads, or Conduct Committee members who are the subject of a complaint to the Conduct Committee will be recused from the process of resolving any such complaint. + +## Responsibility + +The responsibility for administering this Code rests with the Conduct Committee, with oversight by the Executive Director and the Board of Directors. For additional information on the Conduct Committee and its process, please write to . + +## Investigation of Potential Code Violations + +All conflict is not bad as a healthy debate may sometimes be necessary to push us to do our best. It is, however, unacceptable to be disrespectful or offensive, or violate this Code. If you see someone engaging in objectionable behavior violating this Code, we encourage you to address the behavior directly with those involved. If for some reason, you are unable to resolve the matter or feel uncomfortable doing so, or if the behavior is threatening or harassing, please report it following the procedure laid out below. + +Reports should be directed to . It is the Conduct Committee’s role to receive and address reported violations of this Code and to ensure a fair and speedy resolution. + +The Eclipse Foundation takes all reports of potential Code violations seriously and is committed to confidentiality and a full investigation of all allegations. The identity of the reporter will be omitted from the details of the report supplied to the accused. Contributors who are being investigated for a potential Code violation will have an opportunity to be heard prior to any final determination. Those found to have violated the Code can seek reconsideration of the violation and disciplinary action decisions. Every effort will be made to have all matters disposed of within 60 days of the receipt of the complaint. + +## Actions +Contributors who do not follow this Code in good faith may face temporary or permanent repercussions as determined by the Conduct Committee. + +This Code does not address all conduct. It works in conjunction with our [Communication Channel Guidelines](https://www.eclipse.org/org/documents/communication-channel-guidelines/), [Social Media Guidelines](https://www.eclipse.org/org/documents/social_media_guidelines.php), [Bylaws](https://www.eclipse.org/org/documents/eclipse-foundation-be-bylaws-en.pdf), and [Internal Rules](https://www.eclipse.org/org/documents/ef-be-internal-rules.pdf) which set out additional protections for, and obligations of, all contributors. The Foundation has additional policies that provide further guidance on other matters. + +It’s impossible to spell out every possible scenario that might be deemed a violation of this Code. Instead, we rely on one another’s good judgment to uphold a high standard of integrity within all Eclipse Spaces. Sometimes, identifying the right thing to do isn’t an easy call. In such a scenario, raise the issue as early as possible. + +## No Retaliation + +The Eclipse community relies upon and values the help of Contributors who identify potential problems that may need to be addressed within an Eclipse Space. Any retaliation against a Contributor who raises an issue honestly is a violation of this Code. That a Contributor has raised a concern honestly or participated in an investigation, cannot be the basis for any adverse action, including threats, harassment, or discrimination. If you work with someone who has raised a concern or provided information in an investigation, you should continue to treat the person with courtesy and respect. If you believe someone has retaliated against you, report the matter as described by this Code. Honest reporting does not mean that you have to be right when you raise a concern; you just have to believe that the information you are providing is accurate. + +False reporting, especially when intended to retaliate or exclude, is itself a violation of this Code and will not be accepted or tolerated. + +Everyone is encouraged to ask questions about this Code. Your feedback is welcome, and you will get a response within three business days. Write to . + +## Amendments + +The Eclipse Foundation Board of Directors may amend this Code from time to time and may vary the procedures it sets out where appropriate in a particular case. + +### Attribution + +This Code was inspired by the [Contributor Covenant](https://www.contributor-covenant.org/), version 1.4, available [here](https://www.contributor-covenant.org/version/1/4/code-of-conduct/). + +[^1]: Capitalized terms used herein without definition shall have the meanings assigned to them in the Bylaws. \ No newline at end of file diff --git a/CONTRIBUTION.md b/CONTRIBUTION.md index dcc54e64cb3..191ae63fe78 100644 --- a/CONTRIBUTION.md +++ b/CONTRIBUTION.md @@ -1,21 +1,48 @@ -# Eclipse Safe Open Vehicle Core (SCORE) +# Eclipse Safe Open Vehicle Core (S-CORE) The [Eclipse Safe Open Vehicle Core](https://projects.eclipse.org/projects/automotive.score) project aims to develop an open-source core stack for Software Defined Vehicles (SDVs), specifically targeting embedded high-performance Electronic Control Units (ECUs). -Please check the [documentation](https://eclipse-score.github.io) for more information. +Please check the [documentation](https://eclipse-score.github.io/score/main/) for more information. The source code is hosted at [GitHub](https://github.com/eclipse-score). -The communication mainly takes place via the [`score-dev` mailing list](https://accounts.eclipse.org/mailing-list/score-dev) and GitHub issues & pull requests (PR). And we have a chatroom for community discussions here [Eclipse SCORE chatroom](https://chat.eclipse.org/#/room/#automotive.score:matrix.eclipse.org). +The communication mainly takes place via the [`score-dev` mailing list](https://accounts.eclipse.org/mailing-list/score-dev), [Discussions] (https://github.com/orgs/eclipse-score/discussions) and GitHub issues & pull requests (PR). +We have a Slack channel for community discussions here [Eclipse S-CORE Slack Channel](https://sdvworkinggroup.slack.com/archives/C083Z4VL90B). -Please note that for the project the [Eclipse Foundation’s Terms of Use](https://www.eclipse.org/legal/terms-of-use/) apply. -In addition, you need to sign the [ECA](https://www.eclipse.org/legal/ECA.php) and the [DCO](https://www.eclipse.org/legal/dco/) to contribute to the project. ## Contributing + +### Code of Conduct + +Please be familiar with the [Code of Conduct](CODE_OF_CONDUCT.md). + +## Eclipse Contributor Agreement & Developer Certificate of Origin + +Please note that for the project the [Eclipse Foundation’s Terms of Use](https://www.eclipse.org/legal/terms-of-use/) apply. + +Before your contribution can be accepted by the project team contributors must +electronically sign the Eclipse Contributor Agreement (ECA). + +* https://www.eclipse.org/legal/eca/ + + +For more information, please see the Eclipse Committer Handbook: +https://www.eclipse.org/projects/handbook/#resources-commit + +To complete and submit a ECA, log into the +[Eclipse projects forge](https://www.eclipse.org/contribute/cla/) +(you will need to create an account with the Eclipse Foundation if you have not already done so). +Click on "Eclipse Contributor Agreement" and complete the form. +Be sure to use the same email address when you register for the account +that you intend to use when you commit to Git. + +In addition, you need to sign the [DCO](https://www.eclipse.org/legal/dco/) to contribute to the project. + + ### Getting the source code & building the project Please refer to the [README.md](README.md) for further information. ### Getting involved #### Setup Phase -This phase is part of the eclipse Incubation Phase and shall establish all the processes needed for a safe development of functions. Only after this phase it will be possible to contribute code to the project. As the development in this project is driven by requirements, the processes and needed infrastructure incl. tooling will be established based on non-functional Stakeholder_Requirements. During setup phase the contributions are Bug Fixes and Improvements (both on processes and infrastructure). +This phase is part of the eclipse Incubation Phase and shall establish all the processes needed for a safe development of functions. Only after this phase it will be possible to contribute code to the project. As the development in this project is driven by requirements, the processes and needed infrastructure incl. tooling will be established based on }[Non-functional Stakeholder_Requirements](https://eclipse-score.github.io/score/main/requirements/stakeholder/index.html). During setup phase the contributions are Bug Fixes and Improvements (both on processes and infrastructure). #### Bug Fixes and Improvements Improvements are adding/changing processes and infrastructure, bug fixes can be also on development work products like code. @@ -23,13 +50,12 @@ In case you want to fix a bug or contribute an improvement, please perform the f 1) Create a PR by using the corresponding template ([Bugfix PR template](.github/PULL_REQUEST_TEMPLATE/bug_fix.md) or [Improvement PR template](.github/PULL_REQUEST_TEMPLATE/improvement.md)). Please mark your PR as draft until it's ready for review by the Committers (see the [Eclipse Foundation Project Handbook](https://www.eclipse.org/projects/handbook/#contributing-committers) for more information on the role definitions). Improvements are requested by the definition or modification of [Stakeholder Requirements](docs/stakeholder_requirements) or [Tool Requirements](docs/tool_requirements) and may be implemented after acceptance/merge of the request by a second Improvement PR. The needed reviews are automatically triggered via the [CODEOWNERS](.github/CODEOWNERS) file in the repository. 2) Initiate content review by opening a corresponding issue for the PR when it is ready for review. Review of the PR and final merge into the project repository is in responsibility of the Committers. Use the [Bugfix Issue template](.github/ISSUE_TEMPLATE/bug_fix.md) or [Improvement Issue template](.github/ISSUE_TEMPLATE/improvement.md) for this. -Please check here for our Git Commit Rules in the [Configuration_Tool_Guidelines](https://eclipse-score.github.io/score/process_description/guidelines/index.html). +Please check here for our Git Commit Rules in the [Git Guidelines](https://eclipse-score.github.io/score/main/contribute/general/git.html). -Please use the [Stakeholder and Tool Requirements Template](https://eclipse-score.github.io/score/process_description/templates/index.html) when defining these requirements. ![Contribution guide workflow](./docs/_assets/contribution_guide.svg "Contribution guide workflow") #### Additional Information Please note, that all Git commit messages must adhere the rules described in the [Eclipse Foundation Project Handbook](https://www.eclipse.org/projects/handbook/#resources-commit). -Please find process descriptions here: [process description](https://eclipse-score.github.io/score/process_description/). +Please find process descriptions here: [process description](https://eclipse-score.github.io/process_description/main/index.html). From dbc22bff0ea22ef21171dde4e76ea31935a0bfaf Mon Sep 17 00:00:00 2001 From: "markus.schu" Date: Fri, 12 Dec 2025 14:34:07 +0100 Subject: [PATCH 04/25] add process_description update link to release notes add link to maturity levels --- .../score_releases/score_v0_5_beta.rst | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/docs/score_releases/score_releases/score_v0_5_beta.rst b/docs/score_releases/score_releases/score_v0_5_beta.rst index 2dae400e50f..cead9ed3d45 100644 --- a/docs/score_releases/score_releases/score_v0_5_beta.rst +++ b/docs/score_releases/score_releases/score_v0_5_beta.rst @@ -103,8 +103,20 @@ Associated Infrastructure Modules ----------------------------------- process_description -~~~~~~~~~~~~~~~~~~~~~~~ -TBD +~~~~~~~~~~~~~~~~~~~ +Provides a process model establishing organizational rules for developing open source software +in the automotive domain, suitable for safety and security contexts. + +- **Version:** ``process description v1.4.0`` +- **Standards alignment:** + + - ASPICE 4.0 + - ISO 26262 + - ISO 21434 + - ISO PAS 8926 + +- **Release notes**: `process_description release notes `_ +- **Process maturity**: `process_description maturity levels `_ docs-as-code ~~~~~~~~~~~~~~ From 65be69df958d6a63a9a12b2305dd5532f0834362 Mon Sep 17 00:00:00 2001 From: Pawel Rutka Date: Mon, 15 Dec 2025 15:41:06 +0100 Subject: [PATCH 05/25] release: add kyron & orchestrator notes --- .../score_releases/score_v0_5_beta.rst | 34 +++++++++++++++++-- 1 file changed, 31 insertions(+), 3 deletions(-) diff --git a/docs/score_releases/score_releases/score_v0_5_beta.rst b/docs/score_releases/score_releases/score_v0_5_beta.rst index cead9ed3d45..21f142b07f4 100644 --- a/docs/score_releases/score_releases/score_v0_5_beta.rst +++ b/docs/score_releases/score_releases/score_v0_5_beta.rst @@ -78,9 +78,37 @@ Persistency TBD -Orchestrator (Kyron and orchestration framework) -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -TBD +Orchestrator +~~~~~~~~~~~~~ + +**Improvements** + +- Support `log` frontend exchange to: `log`, `tracing` or `score-log` (not yet implemented in this release) +- Increased CIT coverage and stability improvements +- Split of kyron into separate repositories: `orchestrator` and `kyron` + +:Version: ``orchestrator v0.0.4`` +:Source / tag: `Orchestrator GitHub release `__ +:Further reading: See below + + - `Orchestrator scope and design `__ + - `Orchestrator examples `__ + +Kyron +~~~~~~ + +**Improvements** + +- Support `log` frontend exchange to: `log`, `tracing` or `score-log` (not yet implemented in this release) +- Increased CIT coverage and stability improvements +- Split of kyron into separate repositories: `orchestrator` and `kyron` + +:Version: ``kyron v0.0.3`` +:Source / tag: `Kyron GitHub release `__ +:Further reading: See below + + - `Kyron scope and design `__ + - `Kyron examples `__ Reference integration From 6857fe03b73132c11c0e0d75d1e7c1b680db1d6e Mon Sep 17 00:00:00 2001 From: Piotr Korkus Date: Tue, 16 Dec 2025 11:37:30 +0100 Subject: [PATCH 06/25] release: add test scenarios notes --- docs/score_releases/score_releases/score_v0_5_beta.rst | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/score_releases/score_releases/score_v0_5_beta.rst b/docs/score_releases/score_releases/score_v0_5_beta.rst index 21f142b07f4..b40e4fc3a17 100644 --- a/docs/score_releases/score_releases/score_v0_5_beta.rst +++ b/docs/score_releases/score_releases/score_v0_5_beta.rst @@ -160,7 +160,13 @@ TBD Test Scenarios ~~~~~~~~~~~~~~~ -TBD + +**Improvements** +- Refactor tracing subscriber by externalizing it's initialization +- Remove baselibs dependency from C++ scenarios in JSON parsing + +:Version: ``Test Scenarios v0.3.1`` +:Source / tag: `Test Scenarios GitHub release `__ Performed Verification ---------------------- From 4250c2ed236581ec858ec2a10cc5f417f17cf9c7 Mon Sep 17 00:00:00 2001 From: Oliver Pajonk Date: Wed, 17 Dec 2025 11:12:37 +0000 Subject: [PATCH 07/25] Add release notes for EBcLfSA reference integration --- docs/score_releases/score_releases/score_v0_5_beta.rst | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/score_releases/score_releases/score_v0_5_beta.rst b/docs/score_releases/score_releases/score_v0_5_beta.rst index b40e4fc3a17..203bcd7f01a 100644 --- a/docs/score_releases/score_releases/score_v0_5_beta.rst +++ b/docs/score_releases/score_releases/score_v0_5_beta.rst @@ -125,7 +125,11 @@ TBD Reference Elektrobit corbos Linux for Safety Applications Linux image (Experimental) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -TBD + +**Improvements** + +- New ``fastdev`` base image snapshot and corresponding toolchain which include latest security patches and updates. +- Updated packages avoid misleading errors during image start and shutdown, which could be confusing for users. Associated Infrastructure Modules ----------------------------------- From 05003ca85985e675c36214a568930a74a27ec130 Mon Sep 17 00:00:00 2001 From: Oliver Pajonk Date: Wed, 17 Dec 2025 11:12:48 +0000 Subject: [PATCH 08/25] bump devcontainer --- .devcontainer/devcontainer.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.devcontainer/devcontainer.json b/.devcontainer/devcontainer.json index 1a3b163c06d..e88d473e821 100644 --- a/.devcontainer/devcontainer.json +++ b/.devcontainer/devcontainer.json @@ -1,4 +1,4 @@ { "name": "eclipse-s-core", - "image": "ghcr.io/eclipse-score/devcontainer:1.0.0" + "image": "ghcr.io/eclipse-score/devcontainer:v1.1.0" } From 31d4a154f082fe1510587c8c7ee3596f9518765f Mon Sep 17 00:00:00 2001 From: Frank Scholter Peres Date: Wed, 17 Dec 2025 11:46:31 +0000 Subject: [PATCH 09/25] fixes naming --- docs/features/baselibs/index.rst | 2 +- docs/features/communication/index.rst | 2 +- docs/features/frameworks/feo/index.rst | 4 +- docs/features/orchestration/index.rst | 2 +- docs/features/persistency/index.rst | 2 +- .../score_releases/score_v0_5_beta.rst | 42 ++++++++++++++++--- 6 files changed, 43 insertions(+), 11 deletions(-) diff --git a/docs/features/baselibs/index.rst b/docs/features/baselibs/index.rst index c1f16888004..c6a06a9dade 100644 --- a/docs/features/baselibs/index.rst +++ b/docs/features/baselibs/index.rst @@ -14,7 +14,7 @@ .. _baselibs_feature: -Base Libraries (v0.5 alpha) +Base Libraries (v0.5 beta) ########################### .. document:: Base Libraries diff --git a/docs/features/communication/index.rst b/docs/features/communication/index.rst index 176d1806f10..62000c6fc91 100644 --- a/docs/features/communication/index.rst +++ b/docs/features/communication/index.rst @@ -14,7 +14,7 @@ .. _com_feature: -Communication (v0.5 alpha) +Communication (v0.5 beta) ########################## .. document:: Communication diff --git a/docs/features/frameworks/feo/index.rst b/docs/features/frameworks/feo/index.rst index 80ce3f51d73..827455b72c8 100644 --- a/docs/features/frameworks/feo/index.rst +++ b/docs/features/frameworks/feo/index.rst @@ -12,8 +12,8 @@ # SPDX-License-Identifier: Apache-2.0 # ******************************************************************************* -Fixed execution order framework (FEO) -##################################### +Fixed execution order framework (FEO) (v0.5 beta) +################################################# .. document:: Fixed execution order framework :id: doc__frameworks_feo diff --git a/docs/features/orchestration/index.rst b/docs/features/orchestration/index.rst index 54a121fa107..fe5dcb9db09 100644 --- a/docs/features/orchestration/index.rst +++ b/docs/features/orchestration/index.rst @@ -15,7 +15,7 @@ .. _orch_feature: -Orchestration (v0.5 alpha) +Orchestration (v0.5 beta) ########################## .. document:: Orchestration diff --git a/docs/features/persistency/index.rst b/docs/features/persistency/index.rst index e76c5e30e10..418dfc63cd1 100644 --- a/docs/features/persistency/index.rst +++ b/docs/features/persistency/index.rst @@ -12,7 +12,7 @@ # SPDX-License-Identifier: Apache-2.0 # ******************************************************************************* -Persistency (v0.5 alpha) +Persistency (v0.5 beta) ######################## .. toctree:: diff --git a/docs/score_releases/score_releases/score_v0_5_beta.rst b/docs/score_releases/score_releases/score_v0_5_beta.rst index b40e4fc3a17..44d2932f167 100644 --- a/docs/score_releases/score_releases/score_v0_5_beta.rst +++ b/docs/score_releases/score_releases/score_v0_5_beta.rst @@ -29,7 +29,20 @@ S-Core v0.5-beta release notes Overview ^^^^^^^^^ -TBD +This is the second milestone build of the **Eclipse S-CORE platform** (v0.5.0-beta). It brings +together the initial set of core modules, reference integrations, and supporting infrastructure needed to +build and run example applications such as the `scrample `_ +demo on multiple target images. The software architecture and implemented modules are illustrated in the diagram below. + +This release of Eclipse S-CORE is an early beta version intended solely for experimentation, test driving project processes, gaining experience in release creation and soliciting feedback. +Please be aware, that features may be incomplete, the software may exhibit instability or unexpected behavior, and breaking changes and alterations in scope are likely as development progresses. + + +.. image:: ../_assets/architecture.drawio.svg + :width: 1000 + :alt: Architecture overview + :align: center + | @@ -39,7 +52,12 @@ TBD Timeline --------- -TBD +The current timeline for Eclipse S-CORE releases is shown below. + +.. image:: ../_assets/score_release_plan.drawio.svg + :width: 800 + :alt: Architecture overview + :align: center | @@ -47,11 +65,21 @@ For a detailed and always up-to-date planning view, see the `GitHub project `_ +is a “how-to” guide for users getting started with the project or who want to contribute new modules. +It introduces the core concepts of Eclipse S-CORE and walks through building +the ``scrample`` application step by step on top of the platform modules. +It also includes a tutorial for the first application on top of the existing modules. Improvements ^^^^^^^^^^^^^ -TBD +Main focus of this release is to improve the overall stability and performance of the platform, as well as to enhance the usability. +This does include + +- Static code analysis and Execution of Unit testing as part of the `Reference Integration https://github.com/eclipse-score/reference_integration`_. +- A new combined build toolchain of qcc and gcc `bazel cpp toolchain https://github.com/eclipse-score/bazel_cpp_toolchains`_. +- Improved doc-as-code and process description +- Bug Fixes ^^^^^^^^^^^^ @@ -62,7 +90,11 @@ Integrated Software Modules Communication ~~~~~~~~~~~~~ -TBD +Zero-copy, shared-memory based inter-process communication for minimal-latency intra-ECU messaging. + +- **Version:** ``communication v0.1.2`` +- **Source / tag:** `Communication GitHub release `_ +- **Release notes:** :need:`doc__communication_release_note` Fixed Execution Order Framework(FEO) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From 47391340c95707ccde14552ff7dd0333a967f227 Mon Sep 17 00:00:00 2001 From: Frank Scholter Peres Date: Wed, 17 Dec 2025 12:31:58 +0000 Subject: [PATCH 10/25] added descriptions --- .../score_releases/score_v0_5_beta.rst | 59 ++++++++++++++----- 1 file changed, 45 insertions(+), 14 deletions(-) diff --git a/docs/score_releases/score_releases/score_v0_5_beta.rst b/docs/score_releases/score_releases/score_v0_5_beta.rst index 222935b5fdd..376ab9c9731 100644 --- a/docs/score_releases/score_releases/score_v0_5_beta.rst +++ b/docs/score_releases/score_releases/score_v0_5_beta.rst @@ -48,7 +48,7 @@ Please be aware, that features may be incomplete, the software may exhibit insta Highlights ----------- -TBD + Timeline --------- @@ -76,14 +76,15 @@ Improvements Main focus of this release is to improve the overall stability and performance of the platform, as well as to enhance the usability. This does include -- Static code analysis and Execution of Unit testing as part of the `Reference Integration https://github.com/eclipse-score/reference_integration`_. +- Static code analysis with CodeQL and Execution of Unit testing as part of the `Reference Integration https://github.com/eclipse-score/reference_integration`_. - A new combined build toolchain of qcc and gcc `bazel cpp toolchain https://github.com/eclipse-score/bazel_cpp_toolchains`_. - Improved doc-as-code and process description - -Bug Fixes -^^^^^^^^^^^^ -TBD +Bug Fixes Platform +^^^^^^^^^^^^^^^^^^ + +https://github.com/eclipse-score/score/issues?q=is%3Aissue%20state%3Aclosed%20type%3ABug Integrated Software Modules ----------------------------- @@ -98,7 +99,9 @@ Zero-copy, shared-memory based inter-process communication for minimal-latency i Fixed Execution Order Framework(FEO) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -TBD +- **Version:** ``feo v0.1.2`` +- **Source / tag:** `Communication GitHub release `_ +- **Stays at v0.5-alpha** Baselibs ~~~~~~~~~~~~~ @@ -107,8 +110,11 @@ TBD Persistency ~~~~~~~~~~~~~ -TBD +Ensures long-term storage and retrieval of data and provides a reliable mechanism for +preserving application state and data integrity over time. +- **Version:** ``persistency v0.2.1`` +- **Source / tag:** `Persistency GitHub release `_ Orchestrator ~~~~~~~~~~~~~ @@ -145,7 +151,11 @@ Kyron Reference integration ~~~~~~~~~~~~~~~~~~~~~~ -TBD +Central integration of Eclipse S-CORE modules + +- **Version:** ``reference integration v0.5.0-beta`` +- **Source / tag:** `Reference Integration GitHub release `_ + Reference QNX image +++++++++++++++++++++ @@ -184,15 +194,25 @@ in the automotive domain, suitable for safety and security contexts. docs-as-code ~~~~~~~~~~~~~~ -TBD +Tooling for linking and generation of documentation. + +- **Version:** ``docs-as-code v2.2.1`` +- **Source / tag:** `docs-as-code GitHub release `_ tooling ~~~~~~~~~~~~~~ -TBD +Tooling for S-CORE development. + +- **Version:** ``tooling v1.0.4`` +- **Source / tag:** `tooling GitHub release `_ + ITF (Integration Testing Framework) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -TBD +Framework for executing feature integration tests on the reference image. + +- **Version:** ``itf v0.1.0`` +- **Source / tag:** `ITF GitHub release `_ Test Scenarios ~~~~~~~~~~~~~~~ @@ -206,15 +226,26 @@ Test Scenarios Performed Verification ---------------------- -TBD +The following tests were executed as part of this release: + +- All C++ modules built successfully with GCC and QCC toolchains. +- All Rust modules built successfully with the Rust toolchain. +- Each module executed its unit tests. +- Basic integration tests were executed on the reference QNX image in QEMU via the + `release verification `_ workflow +- for **persistency** and **orchestration** modules, component and feature integration tests were executed using the ``score-test-scenarios`` framework; see + `feature_showcase `_ and + `feature_integration_tests `_ for more details. +- Static code analysis of all dependencies with CodeQL MISRA C++2023 package. The results you can find here: https://github.com/eclipse-score/reference_integration/actions/workflows/codeql-multiple-repo-scan.yml Known Issues ---------------------- -- see release notes of every module seperately +- see release notes of every module separately Upgrade Instructions ---------------------- -- TBD +- Increase to newest bazel registry versions: https://github.com/eclipse-score/bazel_registry/tree/main/modules + Contact Information ---------------------- From 01b33d984c14809bc39f0e56f83fbeefb88de609 Mon Sep 17 00:00:00 2001 From: Frank Scholter Peres Date: Wed, 17 Dec 2025 12:51:21 +0000 Subject: [PATCH 11/25] added platform --- .../score_releases/score_v0_5_beta.rst | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/docs/score_releases/score_releases/score_v0_5_beta.rst b/docs/score_releases/score_releases/score_v0_5_beta.rst index 376ab9c9731..0a1d6f7cf2a 100644 --- a/docs/score_releases/score_releases/score_v0_5_beta.rst +++ b/docs/score_releases/score_releases/score_v0_5_beta.rst @@ -24,7 +24,7 @@ S-Core v0.5-beta release notes | **Platform Name**: S-CORE | **Release Tag**: v0.5.0-beta -| **Origin Release Tag**: none - first published release +| **Origin Release Tag**: v0.5.0-alpha | **Release Date**: 2025-12-18 Overview @@ -76,14 +76,19 @@ Improvements Main focus of this release is to improve the overall stability and performance of the platform, as well as to enhance the usability. This does include -- Static code analysis with CodeQL and Execution of Unit testing as part of the `Reference Integration https://github.com/eclipse-score/reference_integration`_. -- A new combined build toolchain of qcc and gcc `bazel cpp toolchain https://github.com/eclipse-score/bazel_cpp_toolchains`_. +- Static code analysis with CodeQL and Execution of Unit testing as part of the `Reference Integration `_. +- A new combined build toolchain of qcc and gcc `bazel cpp toolchain `_. - Improved doc-as-code and process description -- -Bug Fixes Platform + +S-CORE Platform ^^^^^^^^^^^^^^^^^^ +- **Version:** ``score v0.5.2`` +- **Source / tag:** `S-CORE Platform GitHub release `_ +- **Release notes**: `S-CORE Platform release notes `_ + + https://github.com/eclipse-score/score/issues?q=is%3Aissue%20state%3Aclosed%20type%3ABug Integrated Software Modules From c714cc482c370f71e8c0ed7627f9024c1226ec4f Mon Sep 17 00:00:00 2001 From: "Frank Scholter Peres(MBTI)" <145544737+FScholPer@users.noreply.github.com> Date: Wed, 17 Dec 2025 13:52:21 +0100 Subject: [PATCH 12/25] Update CONTRIBUTION.md Co-authored-by: AndreasMittag Signed-off-by: Frank Scholter Peres(MBTI) <145544737+FScholPer@users.noreply.github.com> --- CONTRIBUTION.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTION.md b/CONTRIBUTION.md index 191ae63fe78..0700a9596bf 100644 --- a/CONTRIBUTION.md +++ b/CONTRIBUTION.md @@ -3,7 +3,7 @@ The [Eclipse Safe Open Vehicle Core](https://projects.eclipse.org/projects/autom Please check the [documentation](https://eclipse-score.github.io/score/main/) for more information. The source code is hosted at [GitHub](https://github.com/eclipse-score). -The communication mainly takes place via the [`score-dev` mailing list](https://accounts.eclipse.org/mailing-list/score-dev), [Discussions] (https://github.com/orgs/eclipse-score/discussions) and GitHub issues & pull requests (PR). +The communication mainly takes place via the [`score-dev` mailing list](https://accounts.eclipse.org/mailing-list/score-dev), [Discussions](https://github.com/orgs/eclipse-score/discussions) and GitHub issues & pull requests (PR). We have a Slack channel for community discussions here [Eclipse S-CORE Slack Channel](https://sdvworkinggroup.slack.com/archives/C083Z4VL90B). From a93716ec294c3773f11432d95246721152a3b92b Mon Sep 17 00:00:00 2001 From: Anton Krivoborodov Date: Wed, 17 Dec 2025 15:49:55 +0100 Subject: [PATCH 13/25] add further content --- docs/score_releases/index.rst | 18 +++- .../score_releases/score_v0_5_alpha.rst | 13 --- .../score_releases/score_v0_5_beta.rst | 90 ++++++++++++------- 3 files changed, 75 insertions(+), 46 deletions(-) diff --git a/docs/score_releases/index.rst b/docs/score_releases/index.rst index 035bba0399a..4a841321d57 100644 --- a/docs/score_releases/index.rst +++ b/docs/score_releases/index.rst @@ -24,7 +24,23 @@ See also the project life cycle within the `Eclipse Development Process `_. + +List of S-CORE released versions +--------------------------------- + .. toctree:: - :maxdepth: 1 + :maxdepth: 2 score_releases/index.rst diff --git a/docs/score_releases/score_releases/score_v0_5_alpha.rst b/docs/score_releases/score_releases/score_v0_5_alpha.rst index e3a5d950641..c10a5782c8d 100644 --- a/docs/score_releases/score_releases/score_v0_5_alpha.rst +++ b/docs/score_releases/score_releases/score_v0_5_alpha.rst @@ -52,19 +52,6 @@ Highlights - Initial set of communication, persistency, orchestration, and base utility modules. - Experimental reference images for QNX, Red Hat AutoSD Linux, and EB corbos Linux for Safety Applications. -Timeline ---------- -The current timeline for Eclipse S-CORE releases is shown below. - -.. image:: ../_assets/score_release_plan.drawio.svg - :width: 800 - :alt: Architecture overview - :align: center - -| - -For a detailed and always up-to-date planning view, see the `GitHub project `_. - Eclipse S-CORE book ------------------- The first version of the `Eclipse S-CORE book `_ diff --git a/docs/score_releases/score_releases/score_v0_5_beta.rst b/docs/score_releases/score_releases/score_v0_5_beta.rst index 0a1d6f7cf2a..ab9c68861ef 100644 --- a/docs/score_releases/score_releases/score_v0_5_beta.rst +++ b/docs/score_releases/score_releases/score_v0_5_beta.rst @@ -49,20 +49,6 @@ Please be aware, that features may be incomplete, the software may exhibit insta Highlights ----------- - -Timeline ---------- -The current timeline for Eclipse S-CORE releases is shown below. - -.. image:: ../_assets/score_release_plan.drawio.svg - :width: 800 - :alt: Architecture overview - :align: center - -| - -For a detailed and always up-to-date planning view, see the `GitHub project `_. - Eclipse S-CORE book ------------------- The `Eclipse S-CORE book `_ @@ -71,16 +57,37 @@ It introduces the core concepts of Eclipse S-CORE and walks through building the ``scrample`` application step by step on top of the platform modules. It also includes a tutorial for the first application on top of the existing modules. + Improvements ^^^^^^^^^^^^^ Main focus of this release is to improve the overall stability and performance of the platform, as well as to enhance the usability. This does include -- Static code analysis with CodeQL and Execution of Unit testing as part of the `Reference Integration `_. -- A new combined build toolchain of qcc and gcc `bazel cpp toolchain `_. +- Static code analysis with CodeQL: **//TODO:** add link to the results. +- Execution of Unit tests as part of the Reference Integration `test_integration workflow `_. +- Unit-test coverage measurement results are now automatically part of Release Assests for every component: **//TODO:** link to an example. +- A new combined build toolchain of qcc and gcc, see `bazel_cpp_toolchain <#bazel-cpp-toolchain>`_. - Improved doc-as-code and process description +Software Development Process status +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +The following image provides an overview of the current status of the software development process, the associated tooling, +and the progress of its application to the software modules. + +.. image:: https://raw.githubusercontent.com/eclipse-score/process_description/bec1931b56464543cb70385e75c15fcb1625f0d0/process/_assets/score_process_area_overview.drawio.svg + :width: 1000 + :alt: Architecture overview + :align: center + + +| + +For more details please refer to +`Documentation Management Plan `_, that +provides overview on the process workproduct level for every software module and process area. + + S-CORE Platform ^^^^^^^^^^^^^^^^^^ @@ -94,6 +101,11 @@ https://github.com/eclipse-score/score/issues?q=is%3Aissue%20state%3Aclosed%20ty Integrated Software Modules ----------------------------- + +Baselibs +~~~~~~~~~~~~~ +TBD + Communication ~~~~~~~~~~~~~ Zero-copy, shared-memory based inter-process communication for minimal-latency intra-ECU messaging. @@ -108,10 +120,6 @@ Fixed Execution Order Framework(FEO) - **Source / tag:** `Communication GitHub release `_ - **Stays at v0.5-alpha** -Baselibs -~~~~~~~~~~~~~ -TBD - Persistency ~~~~~~~~~~~~~ @@ -164,11 +172,11 @@ Central integration of Eclipse S-CORE modules Reference QNX image +++++++++++++++++++++ -TBD +- No changes compared to the previous software version. Reference Red Hat AutoSD Linux image (Experimental) +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -TBD +- No changes compared to the previous software version. Reference Elektrobit corbos Linux for Safety Applications Linux image (Experimental) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ @@ -189,10 +197,10 @@ in the automotive domain, suitable for safety and security contexts. - **Version:** ``process description v1.4.0`` - **Standards alignment:** - - ASPICE 4.0 - - ISO 26262 - - ISO 21434 - - ISO PAS 8926 + - ASPICE 4.0 + - ISO 26262 + - ISO 21434 + - ISO PAS 8926 - **Release notes**: `process_description release notes `_ - **Process maturity**: `process_description maturity levels `_ @@ -214,20 +222,38 @@ Tooling for S-CORE development. ITF (Integration Testing Framework) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Framework for executing feature integration tests on the reference image. +- **Improvements** + + - Improved ITF `user documentation `_ - **Version:** ``itf v0.1.0`` - **Source / tag:** `ITF GitHub release `_ Test Scenarios ~~~~~~~~~~~~~~~ +- **Improvements** -**Improvements** -- Refactor tracing subscriber by externalizing it's initialization -- Remove baselibs dependency from C++ scenarios in JSON parsing + - Refactor tracing subscriber by externalizing it's initialization + - Remove baselibs dependency from C++ scenarios in JSON parsing + +- **Version:** ``Test Scenarios v0.3.1`` +- **Source / tag:** `Test Scenarios GitHub release `_ + +Bazel CPP Toolchain +~~~~~~~~~~~~~~~~~~~~ +- **What is in** + + - support for following platform configurations: *x86_64_linux*, *x86_64_qnx*, *arm64_qnx* + - complete feature flag set for the host toolchain (*x86_64_linux*): *minimal*, *strict*, *all_warnings* + +- **What is not in** -:Version: ``Test Scenarios v0.3.1`` -:Source / tag: `Test Scenarios GitHub release `__ + - feature flag set for the target toolchain (infrastructure is already set-up) + - arm64_linux configuration is missing + +- **Version:** ``bazel_cpp_toolchains v0.1.0`` +- **Source / tag:** `Bazel CPP Toolchain release `_ +- **Release notes**: `Bazel CPP Toolchain release notes `_ Performed Verification ---------------------- From 11957a1a3c15bea2345046ff0d0d811af67efca0 Mon Sep 17 00:00:00 2001 From: Frank Scholter Peres Date: Fri, 19 Dec 2025 09:21:29 +0000 Subject: [PATCH 14/25] updated to new --- .../score_releases/score_v0_5_beta.rst | 25 +++++++++++-------- 1 file changed, 15 insertions(+), 10 deletions(-) diff --git a/docs/score_releases/score_releases/score_v0_5_beta.rst b/docs/score_releases/score_releases/score_v0_5_beta.rst index ab9c68861ef..ada367bf5c1 100644 --- a/docs/score_releases/score_releases/score_v0_5_beta.rst +++ b/docs/score_releases/score_releases/score_v0_5_beta.rst @@ -63,14 +63,14 @@ Improvements Main focus of this release is to improve the overall stability and performance of the platform, as well as to enhance the usability. This does include -- Static code analysis with CodeQL: **//TODO:** add link to the results. +- Static code analysis with CodeQL MISRA C++ 2023: `release link `. - Execution of Unit tests as part of the Reference Integration `test_integration workflow `_. -- Unit-test coverage measurement results are now automatically part of Release Assests for every component: **//TODO:** link to an example. +- Unit-test coverage measurement results are now automatically part of Release Assests for every component: **//TODO:** link to an example. - A new combined build toolchain of qcc and gcc, see `bazel_cpp_toolchain <#bazel-cpp-toolchain>`_. - Improved doc-as-code and process description -Software Development Process status +Software Development Process status ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The following image provides an overview of the current status of the software development process, the associated tooling, and the progress of its application to the software modules. @@ -83,7 +83,7 @@ and the progress of its application to the software modules. | -For more details please refer to +For more details please refer to `Documentation Management Plan `_, that provides overview on the process workproduct level for every software module and process area. @@ -126,8 +126,8 @@ Persistency Ensures long-term storage and retrieval of data and provides a reliable mechanism for preserving application state and data integrity over time. -- **Version:** ``persistency v0.2.1`` -- **Source / tag:** `Persistency GitHub release `_ +- **Version:** ``persistency v0.2.2`` +- **Source / tag:** `Persistency GitHub release `_ Orchestrator ~~~~~~~~~~~~~ @@ -176,7 +176,12 @@ Reference QNX image Reference Red Hat AutoSD Linux image (Experimental) +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -- No changes compared to the previous software version. +- Use sub-module structure +- os_images does not need to be a sub-module since it does not use bazel +- Use AutoSD tools to build RPMs (toolchain + bazelrc file) +- Use built RPMs in os_images +- Uses 0.5 modules, similar setup to upstream reference_instegration +- e2e workflow defined in github actions Reference Elektrobit corbos Linux for Safety Applications Linux image (Experimental) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ @@ -209,8 +214,8 @@ docs-as-code ~~~~~~~~~~~~~~ Tooling for linking and generation of documentation. -- **Version:** ``docs-as-code v2.2.1`` -- **Source / tag:** `docs-as-code GitHub release `_ +- **Version:** ``docs-as-code v2.2.0`` +- **Source / tag:** `docs-as-code GitHub release `_ tooling ~~~~~~~~~~~~~~ @@ -250,7 +255,7 @@ Bazel CPP Toolchain - feature flag set for the target toolchain (infrastructure is already set-up) - arm64_linux configuration is missing - + - **Version:** ``bazel_cpp_toolchains v0.1.0`` - **Source / tag:** `Bazel CPP Toolchain release `_ - **Release notes**: `Bazel CPP Toolchain release notes `_ From d5d7eca97dd037d93dbc70d5a1f00d8f9d9bafd8 Mon Sep 17 00:00:00 2001 From: Frank Scholter Peres Date: Fri, 19 Dec 2025 09:43:25 +0000 Subject: [PATCH 15/25] add_beta --- docs/score_releases/score_releases/score_v0_5_beta.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/score_releases/score_releases/score_v0_5_beta.rst b/docs/score_releases/score_releases/score_v0_5_beta.rst index ada367bf5c1..d358efd9648 100644 --- a/docs/score_releases/score_releases/score_v0_5_beta.rst +++ b/docs/score_releases/score_releases/score_v0_5_beta.rst @@ -25,7 +25,7 @@ S-Core v0.5-beta release notes | **Platform Name**: S-CORE | **Release Tag**: v0.5.0-beta | **Origin Release Tag**: v0.5.0-alpha -| **Release Date**: 2025-12-18 +| **Release Date**: 2025-12-19 Overview ^^^^^^^^^ From a028e77a488220857ec946e48c08157c48790109 Mon Sep 17 00:00:00 2001 From: Anton Krivoborodov Date: Fri, 19 Dec 2025 12:11:16 +0100 Subject: [PATCH 16/25] add logging daemon desciption --- .../score_releases/score_v0_5_beta.rst | 35 ++++++++++++++++++- 1 file changed, 34 insertions(+), 1 deletion(-) diff --git a/docs/score_releases/score_releases/score_v0_5_beta.rst b/docs/score_releases/score_releases/score_v0_5_beta.rst index d358efd9648..303c0d77300 100644 --- a/docs/score_releases/score_releases/score_v0_5_beta.rst +++ b/docs/score_releases/score_releases/score_v0_5_beta.rst @@ -68,6 +68,13 @@ This does include - Unit-test coverage measurement results are now automatically part of Release Assests for every component: **//TODO:** link to an example. - A new combined build toolchain of qcc and gcc, see `bazel_cpp_toolchain <#bazel-cpp-toolchain>`_. - Improved doc-as-code and process description +- `bazel_tools_cc `_ introduces a clang-tidy integration into S-CORE bazel infrasturture: + + - Check exhaustive `bazel_tools_cc README `_ and an + `example project `_ for instructions how to set-up + clang-tidy checks for your module + - In the upcoming releases clang-tidy will be extended with custom S-CORE checks to meet necessary process requirements. +- Platform functionality was extended with `logging daemon <#logging-daemon>`_. Software Development Process status @@ -145,8 +152,34 @@ Orchestrator - `Orchestrator scope and design `__ - `Orchestrator examples `__ +Logging Daemon +~~~~~~~~~~~~~~~~~~ + +**Improvements** + +The Eclipse SCORE Logging module provides a comprehensive logging framework for automotive embedded systems, +featuring remote DLT (Diagnostic Log and Trace) capabilities with high-performance, lock-free communication +between applications and the datarouter daemon. + +This is the initial open-source release of the logging framework, +consolidating the complete project structure with build system, dependencies, +and tooling for integration into Eclipse SCORE projects. + +The module is designed for Bazel-based builds and provides both the middleware logging +library (score/mw/log) that includes all supported recorders with respective backends and +the datarouter daemon (score/datarouter). The shared memory implementation between the middleware +library and datarouter daemon guarantees Freedom From Interference (FFI), +enabling safe logging from real-time and safety-critical contexts. + +:Version: ``logging v0.0.3`` +:Source / tag: `logging release `__ +:Further reading: See below + + - `Logging release notes `__ + - `Logging ReadMe `__ + Kyron -~~~~~~ +~~~~~~~~~~~~~~ **Improvements** From fa948d121d3ec2d4df3f070b294b09e51f92e8bd Mon Sep 17 00:00:00 2001 From: "markus.schu" Date: Fri, 19 Dec 2025 12:35:22 +0100 Subject: [PATCH 17/25] replace maturity link for process with current status image --- .../_assets/score_process_area_overview.drawio.svg | 4 ++++ .../score_releases/score_releases/score_v0_5_beta.rst | 11 ++++++++--- 2 files changed, 12 insertions(+), 3 deletions(-) create mode 100644 docs/score_releases/_assets/score_process_area_overview.drawio.svg diff --git a/docs/score_releases/_assets/score_process_area_overview.drawio.svg b/docs/score_releases/_assets/score_process_area_overview.drawio.svg new file mode 100644 index 00000000000..6bfc2a76b5f --- /dev/null +++ b/docs/score_releases/_assets/score_process_area_overview.drawio.svg @@ -0,0 +1,4 @@ + + + +







Process Areas - Support










 
Process Areas - Support...




Process Areas - Development










 
Process Areas - Development...
Introduction
Introduction









Process Areas - Management












 
Process Areas - Management...
Requirements
Engineering
Requirements...
Safety
Management
Safety...
Change Management
Change Managem...
Documentation
Management
Documentation...
General Concepts
General Concepts
Standards
Standards
Roles
Roles


Architecture



Architecture...

Imple-mentation
(Detailed Design,
Coding)
Imple-mentatio...
Problem Resolution
Problem Resolu...
ML 4
ML 4
ML 2
ML 2
ML 1
ML 1
Verification

Verification...
Configuration
Management
Configuration...
Tool
Management
Tool...
Quality
Management
Quality...
Platform
Management
Platform...
Maturity Level
Maturity Level
ML 0
ML 0

Safety
Analysis

Safety...
Work Products
Work Products
Workflows
Workflows
ML 3
ML 3
Plan - 
Process definition planned
Documents not available or most empty
Plan -...
Initial - 
Process definition in place, but not yet compliant, consistency across S-CORE platform, modules and repeatability of processes may not be possible.
Documents are mostly available, main parts done, principles clear, all top level questions addressed, well structured.
Initial -...
Managed -
Process definition in place but not yet deployed in S-CORE, but execution would allow consistency across S-CORE platform and modules, repeatability of processes possible
Documents are complete, documented on a comprehensible systematic approach, verified, only minor questions open, Process requirements (of highest priority) enforced by implemented Tool Requirements (or a feasible manual work around is defined).
Managed -...
Defined/Practiced - 
Deployed (at least once) in S-CORE platform or one Module, The processes have been practiced, and evidence exists to demonstrate that this has occurred. 
Documents are complete, verified and released, Process Requirements (of high/ medium priority) enforced by implemented Tool Requirements, Tool evaluation performed
 Initial Safety Audit passed.
Defined/Practiced -...
Improving - 
Deployed on S-CORE platform and various S-CORE Modules and constantly improving, using suitable process metrics, S-CORE commiter control the effectiveness and performance of the platform and modules and demonstrate continuous improvement in these areas. Tool qualification available.
Improving -...
Release
Management
Release...
Trustable
Trustable
Folder Templates
Folder Templates
Security
Management
Security...
Security
Analysis
Security...Text is not SVG - cannot display diff --git a/docs/score_releases/score_releases/score_v0_5_beta.rst b/docs/score_releases/score_releases/score_v0_5_beta.rst index 303c0d77300..be001ad3395 100644 --- a/docs/score_releases/score_releases/score_v0_5_beta.rst +++ b/docs/score_releases/score_releases/score_v0_5_beta.rst @@ -70,11 +70,11 @@ This does include - Improved doc-as-code and process description - `bazel_tools_cc `_ introduces a clang-tidy integration into S-CORE bazel infrasturture: - - Check exhaustive `bazel_tools_cc README `_ and an + - Check exhaustive `bazel_tools_cc README `_ and an `example project `_ for instructions how to set-up clang-tidy checks for your module - In the upcoming releases clang-tidy will be extended with custom S-CORE checks to meet necessary process requirements. -- Platform functionality was extended with `logging daemon <#logging-daemon>`_. +- Platform functionality was extended with `logging daemon <#logging-daemon>`_. Software Development Process status @@ -241,7 +241,12 @@ in the automotive domain, suitable for safety and security contexts. - ISO PAS 8926 - **Release notes**: `process_description release notes `_ -- **Process maturity**: `process_description maturity levels `_ +- **Process maturity overview**: + +.. figure:: ../_assets/score_process_area_overview.drawio.svg + :width: 100% + :align: center + :alt: Process area overview for the **Project** docs-as-code ~~~~~~~~~~~~~~ From 2e49652b9dfc9064bb2108a3c52dcc41451a3a00 Mon Sep 17 00:00:00 2001 From: Anton Krivoborodov Date: Fri, 19 Dec 2025 12:55:42 +0100 Subject: [PATCH 18/25] add baselibs release notes --- .../score_releases/score_v0_5_beta.rst | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/docs/score_releases/score_releases/score_v0_5_beta.rst b/docs/score_releases/score_releases/score_v0_5_beta.rst index be001ad3395..6fe48deecb8 100644 --- a/docs/score_releases/score_releases/score_v0_5_beta.rst +++ b/docs/score_releases/score_releases/score_v0_5_beta.rst @@ -108,10 +108,14 @@ https://github.com/eclipse-score/score/issues?q=is%3Aissue%20state%3Aclosed%20ty Integrated Software Modules ----------------------------- - Baselibs ~~~~~~~~~~~~~ -TBD +Selection of basic C++ utility libraries for common use in the S-CORE project + +- **Version:** ``baselibs v0.2.2`` +- **Source / tag:** `Baselibs GitHub release `_ +- **Release notes**: `Baselibs release notes `_ + Communication ~~~~~~~~~~~~~ @@ -158,8 +162,8 @@ Logging Daemon **Improvements** The Eclipse SCORE Logging module provides a comprehensive logging framework for automotive embedded systems, -featuring remote DLT (Diagnostic Log and Trace) capabilities with high-performance, lock-free communication -between applications and the datarouter daemon. +featuring remote DLT (Diagnostic Log and Trace) capabilities with +lock-free communication between applications and the datarouter daemon. This is the initial open-source release of the logging framework, consolidating the complete project structure with build system, dependencies, From 7525bf866fb1f3baa653d2d95e741d9543de60fc Mon Sep 17 00:00:00 2001 From: Anton Krivoborodov Date: Fri, 19 Dec 2025 13:19:50 +0100 Subject: [PATCH 19/25] further improvement --- .../score_releases/score_v0_5_beta.rst | 70 +++++++++---------- 1 file changed, 32 insertions(+), 38 deletions(-) diff --git a/docs/score_releases/score_releases/score_v0_5_beta.rst b/docs/score_releases/score_releases/score_v0_5_beta.rst index 6fe48deecb8..669febdf07e 100644 --- a/docs/score_releases/score_releases/score_v0_5_beta.rst +++ b/docs/score_releases/score_releases/score_v0_5_beta.rst @@ -66,7 +66,7 @@ This does include - Static code analysis with CodeQL MISRA C++ 2023: `release link `. - Execution of Unit tests as part of the Reference Integration `test_integration workflow `_. - Unit-test coverage measurement results are now automatically part of Release Assests for every component: **//TODO:** link to an example. -- A new combined build toolchain of qcc and gcc, see `bazel_cpp_toolchain <#bazel-cpp-toolchain>`_. +- A new combined build toolchain of qcc and gcc, see :ref:`bazel-cpp-toolchain `. - Improved doc-as-code and process description - `bazel_tools_cc `_ introduces a clang-tidy integration into S-CORE bazel infrasturture: @@ -74,25 +74,7 @@ This does include `example project `_ for instructions how to set-up clang-tidy checks for your module - In the upcoming releases clang-tidy will be extended with custom S-CORE checks to meet necessary process requirements. -- Platform functionality was extended with `logging daemon <#logging-daemon>`_. - - -Software Development Process status -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -The following image provides an overview of the current status of the software development process, the associated tooling, -and the progress of its application to the software modules. - -.. image:: https://raw.githubusercontent.com/eclipse-score/process_description/bec1931b56464543cb70385e75c15fcb1625f0d0/process/_assets/score_process_area_overview.drawio.svg - :width: 1000 - :alt: Architecture overview - :align: center - - -| - -For more details please refer to -`Documentation Management Plan `_, that -provides overview on the process workproduct level for every software module and process area. +- Platform functionality was extended with :ref:`logging daemon `. S-CORE Platform @@ -125,6 +107,7 @@ Zero-copy, shared-memory based inter-process communication for minimal-latency i - **Source / tag:** `Communication GitHub release `_ - **Release notes:** :need:`doc__communication_release_note` + Fixed Execution Order Framework(FEO) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - **Version:** ``feo v0.1.2`` @@ -140,21 +123,7 @@ preserving application state and data integrity over time. - **Version:** ``persistency v0.2.2`` - **Source / tag:** `Persistency GitHub release `_ -Orchestrator -~~~~~~~~~~~~~ - -**Improvements** - -- Support `log` frontend exchange to: `log`, `tracing` or `score-log` (not yet implemented in this release) -- Increased CIT coverage and stability improvements -- Split of kyron into separate repositories: `orchestrator` and `kyron` - -:Version: ``orchestrator v0.0.4`` -:Source / tag: `Orchestrator GitHub release `__ -:Further reading: See below - - - `Orchestrator scope and design `__ - - `Orchestrator examples `__ +.. _logging_daemon: Logging Daemon ~~~~~~~~~~~~~~~~~~ @@ -175,13 +144,31 @@ the datarouter daemon (score/datarouter). The shared memory implementation betwe library and datarouter daemon guarantees Freedom From Interference (FFI), enabling safe logging from real-time and safety-critical contexts. -:Version: ``logging v0.0.3`` -:Source / tag: `logging release `__ -:Further reading: See below +- **Version:** ``logging v0.0.3`` +- **VSource / tag:** `logging release `__ +- **Further reading:**: See below - `Logging release notes `__ - `Logging ReadMe `__ + +Orchestrator +~~~~~~~~~~~~~ + +**Improvements** + +- Support `log` frontend exchange to: `log`, `tracing` or `score-log` (not yet implemented in this release) +- Increased CIT coverage and stability improvements +- Split of kyron into separate repositories: `orchestrator` and `kyron` + +:Version: ``orchestrator v0.0.4`` +:Source / tag: `Orchestrator GitHub release `__ +:Further reading: See below + + - `Orchestrator scope and design `__ + - `Orchestrator examples `__ + + Kyron ~~~~~~~~~~~~~~ @@ -252,6 +239,11 @@ in the automotive domain, suitable for safety and security contexts. :align: center :alt: Process area overview for the **Project** +For more details please refer to +`Documentation Management Plan `_, that +provides process workproduct level overview for every software module and process area. + + docs-as-code ~~~~~~~~~~~~~~ Tooling for linking and generation of documentation. @@ -286,6 +278,8 @@ Test Scenarios - **Version:** ``Test Scenarios v0.3.1`` - **Source / tag:** `Test Scenarios GitHub release `_ +.. _bazel_cpp_toolchain: + Bazel CPP Toolchain ~~~~~~~~~~~~~~~~~~~~ - **What is in** From 45254feff95d366cfd8ae97bf9c310050d3bbfe3 Mon Sep 17 00:00:00 2001 From: Ulrich Huber Date: Fri, 19 Dec 2025 14:34:38 +0100 Subject: [PATCH 20/25] Add release notes for communication Signed-off-by: Ulrich Huber --- docs/score_releases/score_releases/score_v0_5_beta.rst | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/score_releases/score_releases/score_v0_5_beta.rst b/docs/score_releases/score_releases/score_v0_5_beta.rst index 669febdf07e..ec431445ab3 100644 --- a/docs/score_releases/score_releases/score_v0_5_beta.rst +++ b/docs/score_releases/score_releases/score_v0_5_beta.rst @@ -107,6 +107,11 @@ Zero-copy, shared-memory based inter-process communication for minimal-latency i - **Source / tag:** `Communication GitHub release `_ - **Release notes:** :need:`doc__communication_release_note` +**Improvements** + +- Enabled various code quality tools +- Extension of the Rust API (expect further extensive work on this API) +- Support explicit setting of application id in configuration (with fallback to PID) Fixed Execution Order Framework(FEO) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From 277ee7c5d66a5538604e0280f4c0c5ab2348f93b Mon Sep 17 00:00:00 2001 From: "Frank Scholter Peres(MBTI)" <145544737+FScholPer@users.noreply.github.com> Date: Fri, 19 Dec 2025 17:12:13 +0100 Subject: [PATCH 21/25] Update CONTRIBUTION.md Co-authored-by: AndreasMittag Signed-off-by: Frank Scholter Peres(MBTI) <145544737+FScholPer@users.noreply.github.com> --- CONTRIBUTION.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTION.md b/CONTRIBUTION.md index 0700a9596bf..d8f89f084d3 100644 --- a/CONTRIBUTION.md +++ b/CONTRIBUTION.md @@ -42,7 +42,7 @@ Please refer to the [README.md](README.md) for further information. ### Getting involved #### Setup Phase -This phase is part of the eclipse Incubation Phase and shall establish all the processes needed for a safe development of functions. Only after this phase it will be possible to contribute code to the project. As the development in this project is driven by requirements, the processes and needed infrastructure incl. tooling will be established based on }[Non-functional Stakeholder_Requirements](https://eclipse-score.github.io/score/main/requirements/stakeholder/index.html). During setup phase the contributions are Bug Fixes and Improvements (both on processes and infrastructure). +This phase is part of the eclipse Incubation Phase and shall establish all the processes needed for a safe development of functions. Only after this phase it will be possible to contribute code to the project. As the development in this project is driven by requirements, the processes and needed infrastructure incl. tooling will be established based on [Non-functional Stakeholder_Requirements](https://eclipse-score.github.io/score/main/requirements/stakeholder/index.html). During setup phase the contributions are Bug Fixes and Improvements (both on processes and infrastructure). #### Bug Fixes and Improvements Improvements are adding/changing processes and infrastructure, bug fixes can be also on development work products like code. From 908dcb8c1f13a2f7ebaed7ad41683ff876a5e08b Mon Sep 17 00:00:00 2001 From: Frank Scholter Peres Date: Fri, 19 Dec 2025 17:18:40 +0100 Subject: [PATCH 22/25] fixed review comments --- CODE_OF_CONDUCT.md | 93 ------------------- .../score_releases/score_v0_5_beta.rst | 14 +-- 2 files changed, 8 insertions(+), 99 deletions(-) delete mode 100644 CODE_OF_CONDUCT.md diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md deleted file mode 100644 index faa735b35e4..00000000000 --- a/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,93 +0,0 @@ -# Community Code of Conduct - -**Version 2.0 -January 1, 2023** - -## Our Pledge - -In the interest of fostering an open and welcoming environment, we as community members, contributors, Committers[^1], and Project Leads (collectively "Contributors") pledge to make participation in our projects and our community a harassment-free and inclusive experience for everyone. - -This Community Code of Conduct ("Code") outlines our behavior expectations as members of our community in all Eclipse Foundation activities, both offline and online. It is not intended to govern scenarios or behaviors outside of the scope of Eclipse Foundation activities. Nor is it intended to replace or supersede the protections offered to all our community members under the law. Please follow both the spirit and letter of this Code and encourage other Contributors to follow these principles into our work. Failure to read or acknowledge this Code does not excuse a Contributor from compliance with the Code. - -## Our Standards - -Examples of behavior that contribute to creating a positive and professional environment include: - -- Using welcoming and inclusive language; -- Actively encouraging all voices; -- Helping others bring their perspectives and listening actively. If you find yourself dominating a discussion, it is especially important to encourage other voices to join in; -- Being respectful of differing viewpoints and experiences; -- Gracefully accepting constructive criticism; -- Focusing on what is best for the community; -- Showing empathy towards other community members; -- Being direct but professional; and -- Leading by example by holding yourself and others accountable - -Examples of unacceptable behavior by Contributors include: - -- The use of sexualized language or imagery; -- Unwelcome sexual attention or advances; -- Trolling, insulting/derogatory comments, and personal or political attacks; -- Public or private harassment, repeated harassment; -- Publishing others' private information, such as a physical or electronic address, without explicit permission; -- Violent threats or language directed against another person; -- Sexist, racist, or otherwise discriminatory jokes and language; -- Posting sexually explicit or violent material; -- Sharing private content, such as emails sent privately or non-publicly, or unlogged forums such as IRC channel history; -- Personal insults, especially those using racist or sexist terms; -- Excessive or unnecessary profanity; -- Advocating for, or encouraging, any of the above behavior; and -- Other conduct which could reasonably be considered inappropriate in a professional setting - -## Our Responsibilities - -With the support of the Eclipse Foundation employees, consultants, officers, and directors (collectively, the "Staff"), Committers, and Project Leads, the Eclipse Foundation Conduct Committee (the "Conduct Committee") is responsible for clarifying the standards of acceptable behavior. The Conduct Committee takes appropriate and fair corrective action in response to any instances of unacceptable behavior. - -## Scope - -This Code applies within all Project, Working Group, and Interest Group spaces and communication channels of the Eclipse Foundation (collectively, "Eclipse spaces"), within any Eclipse-organized event or meeting, and in public spaces when an individual is representing an Eclipse Foundation Project, Working Group, Interest Group, or their communities. Examples of representing a Project or community include posting via an official social media account, personal accounts, or acting as an appointed representative at an online or offline event. Representation of Projects, Working Groups, and Interest Groups may be further defined and clarified by Committers, Project Leads, or the Staff. - -## Enforcement - -Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the Conduct Committee via conduct@eclipse-foundation.org. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. Without the explicit consent of the reporter, the Conduct Committee is obligated to maintain confidentiality with regard to the reporter of an incident. The Conduct Committee is further obligated to ensure that the respondent is provided with sufficient information about the complaint to reply. If such details cannot be provided while maintaining confidentiality, the Conduct Committee will take the respondent‘s inability to provide a defense into account in its deliberations and decisions. Further details of enforcement guidelines may be posted separately. - -Staff, Committers and Project Leads have the right to report, remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code, or to block temporarily or permanently any Contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. Any such actions will be reported to the Conduct Committee for transparency and record keeping. - -Any Staff (including officers and directors of the Eclipse Foundation), Committers, Project Leads, or Conduct Committee members who are the subject of a complaint to the Conduct Committee will be recused from the process of resolving any such complaint. - -## Responsibility - -The responsibility for administering this Code rests with the Conduct Committee, with oversight by the Executive Director and the Board of Directors. For additional information on the Conduct Committee and its process, please write to . - -## Investigation of Potential Code Violations - -All conflict is not bad as a healthy debate may sometimes be necessary to push us to do our best. It is, however, unacceptable to be disrespectful or offensive, or violate this Code. If you see someone engaging in objectionable behavior violating this Code, we encourage you to address the behavior directly with those involved. If for some reason, you are unable to resolve the matter or feel uncomfortable doing so, or if the behavior is threatening or harassing, please report it following the procedure laid out below. - -Reports should be directed to . It is the Conduct Committee’s role to receive and address reported violations of this Code and to ensure a fair and speedy resolution. - -The Eclipse Foundation takes all reports of potential Code violations seriously and is committed to confidentiality and a full investigation of all allegations. The identity of the reporter will be omitted from the details of the report supplied to the accused. Contributors who are being investigated for a potential Code violation will have an opportunity to be heard prior to any final determination. Those found to have violated the Code can seek reconsideration of the violation and disciplinary action decisions. Every effort will be made to have all matters disposed of within 60 days of the receipt of the complaint. - -## Actions -Contributors who do not follow this Code in good faith may face temporary or permanent repercussions as determined by the Conduct Committee. - -This Code does not address all conduct. It works in conjunction with our [Communication Channel Guidelines](https://www.eclipse.org/org/documents/communication-channel-guidelines/), [Social Media Guidelines](https://www.eclipse.org/org/documents/social_media_guidelines.php), [Bylaws](https://www.eclipse.org/org/documents/eclipse-foundation-be-bylaws-en.pdf), and [Internal Rules](https://www.eclipse.org/org/documents/ef-be-internal-rules.pdf) which set out additional protections for, and obligations of, all contributors. The Foundation has additional policies that provide further guidance on other matters. - -It’s impossible to spell out every possible scenario that might be deemed a violation of this Code. Instead, we rely on one another’s good judgment to uphold a high standard of integrity within all Eclipse Spaces. Sometimes, identifying the right thing to do isn’t an easy call. In such a scenario, raise the issue as early as possible. - -## No Retaliation - -The Eclipse community relies upon and values the help of Contributors who identify potential problems that may need to be addressed within an Eclipse Space. Any retaliation against a Contributor who raises an issue honestly is a violation of this Code. That a Contributor has raised a concern honestly or participated in an investigation, cannot be the basis for any adverse action, including threats, harassment, or discrimination. If you work with someone who has raised a concern or provided information in an investigation, you should continue to treat the person with courtesy and respect. If you believe someone has retaliated against you, report the matter as described by this Code. Honest reporting does not mean that you have to be right when you raise a concern; you just have to believe that the information you are providing is accurate. - -False reporting, especially when intended to retaliate or exclude, is itself a violation of this Code and will not be accepted or tolerated. - -Everyone is encouraged to ask questions about this Code. Your feedback is welcome, and you will get a response within three business days. Write to . - -## Amendments - -The Eclipse Foundation Board of Directors may amend this Code from time to time and may vary the procedures it sets out where appropriate in a particular case. - -### Attribution - -This Code was inspired by the [Contributor Covenant](https://www.contributor-covenant.org/), version 1.4, available [here](https://www.contributor-covenant.org/version/1/4/code-of-conduct/). - -[^1]: Capitalized terms used herein without definition shall have the meanings assigned to them in the Bylaws. \ No newline at end of file diff --git a/docs/score_releases/score_releases/score_v0_5_beta.rst b/docs/score_releases/score_releases/score_v0_5_beta.rst index ec431445ab3..091e4b98031 100644 --- a/docs/score_releases/score_releases/score_v0_5_beta.rst +++ b/docs/score_releases/score_releases/score_v0_5_beta.rst @@ -205,12 +205,14 @@ Reference QNX image Reference Red Hat AutoSD Linux image (Experimental) +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -- Use sub-module structure -- os_images does not need to be a sub-module since it does not use bazel -- Use AutoSD tools to build RPMs (toolchain + bazelrc file) -- Use built RPMs in os_images -- Uses 0.5 modules, similar setup to upstream reference_instegration -- e2e workflow defined in github actions +- Uses AutoSD's toolchain to build and generate Lola RPMs +- Deploy RPMs into an AutoSD Image + +Pull requests: + +https://github.com/eclipse-score/reference_integration/pull/56 +https://github.com/eclipse-score/inc_os_autosd/pull/16 + Reference Elektrobit corbos Linux for Safety Applications Linux image (Experimental) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ From 1662068a9ead6bd4f41fed8941a8922e29d50c1e Mon Sep 17 00:00:00 2001 From: "Frank Scholter Peres(MBTI)" <145544737+FScholPer@users.noreply.github.com> Date: Fri, 19 Dec 2025 17:28:26 +0100 Subject: [PATCH 23/25] Update docs/handbook/own_application/index.rst Co-authored-by: Oliver Pajonk Signed-off-by: Frank Scholter Peres(MBTI) <145544737+FScholPer@users.noreply.github.com> --- docs/handbook/own_application/index.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/handbook/own_application/index.rst b/docs/handbook/own_application/index.rst index 3d7c0ba787c..336e2568443 100644 --- a/docs/handbook/own_application/index.rst +++ b/docs/handbook/own_application/index.rst @@ -116,7 +116,7 @@ Be aware that the version numbers change over time. Always check the latest vers common --@score-baselibs//score/json:base_library=nlohmann common --@communication//score/mw/com/flags:tracing_library=stub - common --registry=https://raw.githubusercontent.com/eclipse-score/bazel_registry/v0.5.0-alpha/ + common --registry=https://raw.githubusercontent.com/eclipse-score/bazel_registry/v0.5.0-beta/ common --registry=https://bcr.bazel.build From 9e765ec71600634dcbd613c77a51ed50205f7142 Mon Sep 17 00:00:00 2001 From: "Frank Scholter Peres(MBTI)" <145544737+FScholPer@users.noreply.github.com> Date: Fri, 19 Dec 2025 17:28:42 +0100 Subject: [PATCH 24/25] Update docs/handbook/own_application/index.rst Co-authored-by: Oliver Pajonk Signed-off-by: Frank Scholter Peres(MBTI) <145544737+FScholPer@users.noreply.github.com> --- docs/handbook/own_application/index.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/handbook/own_application/index.rst b/docs/handbook/own_application/index.rst index 336e2568443..52589de88ee 100644 --- a/docs/handbook/own_application/index.rst +++ b/docs/handbook/own_application/index.rst @@ -132,7 +132,7 @@ You can now either continue with this guide to create a minimal consumer-produce ------------ -1. Use it :) +2. Use it :) ------------ Once your project is set up, you can start sending and receiving messages. From 80cc7b4b353e5a3c24857e3e32bf54d1672c8834 Mon Sep 17 00:00:00 2001 From: "Frank Scholter Peres(MBTI)" <145544737+FScholPer@users.noreply.github.com> Date: Fri, 19 Dec 2025 17:30:58 +0100 Subject: [PATCH 25/25] Update docs/score_releases/score_releases/score_v0_5_beta.rst Co-authored-by: Oliver Pajonk Signed-off-by: Frank Scholter Peres(MBTI) <145544737+FScholPer@users.noreply.github.com> --- docs/score_releases/score_releases/score_v0_5_beta.rst | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/score_releases/score_releases/score_v0_5_beta.rst b/docs/score_releases/score_releases/score_v0_5_beta.rst index 091e4b98031..2267d8100aa 100644 --- a/docs/score_releases/score_releases/score_v0_5_beta.rst +++ b/docs/score_releases/score_releases/score_v0_5_beta.rst @@ -85,7 +85,6 @@ S-CORE Platform - **Release notes**: `S-CORE Platform release notes `_ -https://github.com/eclipse-score/score/issues?q=is%3Aissue%20state%3Aclosed%20type%3ABug Integrated Software Modules -----------------------------