From 835eee335839a2c4bfdfe20921c2672e1ae8face Mon Sep 17 00:00:00 2001 From: "jhr2hi@bosch.com" Date: Wed, 13 May 2026 11:37:02 +0200 Subject: [PATCH 1/2] move folder of release notes to right repository --- docs/contribute/general/folder.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/contribute/general/folder.rst b/docs/contribute/general/folder.rst index 4edde5bb58d..2e6ea628c0e 100644 --- a/docs/contribute/general/folder.rst +++ b/docs/contribute/general/folder.rst @@ -66,14 +66,11 @@ The following shows the folder structure of the platform repository (ordered alp │ [:need:`wp__platform_dfa`], [:need:`wp__platform_safety_manual`], │ [:need:`wp__platform_safety_package`], [:need:`wp__fdr_reports`], │ [:need:`wp__audit_report`] - ├── score_releases/ -> [:need:`wp__platform_sw_release_note`] ├── score_tools/ -> Tool list and [:need:`wp__tool_verification_report`] ├── security/ -> Security documentation on platform level: │ [:need:`wp__platform_security_manual`], [:need:`wp__platform_security_package`], │ [:need:`wp__sw_platform_sbom`], [:need:`wp__platform_security_analysis`], │ [:need:`wp__audit_report_security`] - ├── verification_report/ -> Platform verification report (reporting all platform feature's verifications) - │ [:need:`wp__verification_platform_ver_report`] └── tools/ -> Platform tools (not covered in tool repositories) └── decision_records/ -> Design decision records for tools on platform level README.md -> Entrypoint of the repository @@ -108,7 +105,10 @@ cross-repository builds and detect integration issues early in the development c rust_coverage/ -> Rust coverage configuration scripts/ -> Internal tooling scripts (known_good management, workspace metadata generation, etc.) + score_releases/ -> [:need:`wp__platform_sw_release_note`] showcases/ -> S-CORE wide showcases deployed into images + verification_report/ -> Platform verification report (reporting all platform feature's verifications) + [:need:`wp__verification_platform_ver_report`] score_starter -> Launcher script to select and run an integration scenario tooling/ -> Single point of interaction with all tooling artifacts MODULE.bazel -> Bazel module definition From 41bdc5fbb2c3cf42e82cce3f2a19e83204aa1147 Mon Sep 17 00:00:00 2001 From: "jhr2hi@bosch.com" Date: Wed, 13 May 2026 11:50:52 +0200 Subject: [PATCH 2/2] move it to docs --- docs/contribute/general/folder.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/contribute/general/folder.rst b/docs/contribute/general/folder.rst index 2e6ea628c0e..54e479cd1d1 100644 --- a/docs/contribute/general/folder.rst +++ b/docs/contribute/general/folder.rst @@ -92,6 +92,9 @@ cross-repository builds and detect integration issues early in the development c ci/ -> CI configuration and scripts cli/ -> CLI tool running on the target to guide users through examples docs/ -> Documentation of the reference integration + ├── score_releases/ -> [:need:`wp__platform_sw_release_note`] + └── verification_report/ -> Platform verification report (reporting all platform feature's verifications) + [:need:`wp__verification_platform_ver_report`] images/ -> Concrete images for each target platform as Bazel modules. Each platform has its own folder named ``platform_arch``, e.g. ``qnx_aarch64``, ``autosd_x86_64``, ``ebclfsa_aarch64``, @@ -105,10 +108,7 @@ cross-repository builds and detect integration issues early in the development c rust_coverage/ -> Rust coverage configuration scripts/ -> Internal tooling scripts (known_good management, workspace metadata generation, etc.) - score_releases/ -> [:need:`wp__platform_sw_release_note`] showcases/ -> S-CORE wide showcases deployed into images - verification_report/ -> Platform verification report (reporting all platform feature's verifications) - [:need:`wp__verification_platform_ver_report`] score_starter -> Launcher script to select and run an integration scenario tooling/ -> Single point of interaction with all tooling artifacts MODULE.bazel -> Bazel module definition