dont use score main releasenotes

Author: RolandJentschETAS

docs/conf.py

@@ -25,6 +25,14 @@
     "score_sphinx_bundle",
 ]
 
+# Exclude external release notes that are now maintained locally in docs/score_releases/
+exclude_patterns = [
+    "_collections/score_platform/docs/score_releases/score_releases/**",
+]
+
+# Suppress toc.excluded warnings from external modules referencing excluded docs
+suppress_warnings = ["toc.excluded"]
+
 # Enable markdown rendering
 source_suffix = {
     ".rst": "restructuredtext",

docs/index.rst

@@ -15,18 +15,21 @@
 Reference Integration Documentation
 ===================================
 
-Newest Release Notes
---------------------
-
-:doc:`score_releases/release_note_score_v0_7`
-
 Current Integration Status Overview
 -----------------------------------
 
 `View dashboard (points always to main for now) <https://eclipse-score.github.io/reference_integration/main/status_dashboard.html>`_
 
 Explore the documentation
 -------------------------
+
+.. toctree::
+   :glob:
+   :caption: S-CORE Releases
+   :maxdepth: 2
+
+   score_releases/index
+
 .. toctree::
    :caption: Software Components
    :titlesonly:
@@ -55,9 +58,3 @@ Explore the documentation
 
    verification_report/platform_verification_report
 
-.. toctree::
-   :glob:
-   :caption: S-CORE Releases
-   :maxdepth: 2
-
-   score_releases/index

docs/score_releases/release_note_score_v0_5_alpha.rst

@@ -16,7 +16,7 @@ S-CORE Platform v0.5-alpha release note
 =======================================
 
 .. document:: S-Core v0.5-alpha release note
-   :id: doc__score_v0_5_alpha_release_note
+   :id: doc__score_v05_alpha_release_note
    :status: valid
    :safety: ASIL_B
    :security: YES

docs/score_releases/release_note_score_v0_5_beta.rst

@@ -66,15 +66,15 @@ This does include
 - Static code analysis with CodeQL MISRA C++ 2023: `release link <https://github.com/eclipse-score/reference_integration/releases/tag/v0.5.0-beta>`.
 - Execution of Unit tests as part of the Reference Integration `test_integration workflow <https://github.com/eclipse-score/reference_integration/blob/main/.github/workflows/test_integration.yml>`_.
 - 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 :ref:`bazel-cpp-toolchain <bazel_cpp_toolchain>`.
+- A new combined build toolchain of qcc and gcc, see `bazel-cpp-toolchain <https://github.com/eclipse-score/bazel_cpp_toolchains>`_.
 - Improved doc-as-code and process description
 - `bazel_tools_cc <https://github.com/eclipse-score/bazel-tools-cc>`_ introduces a clang-tidy integration into S-CORE bazel infrasturture:
 
   - Check exhaustive `bazel_tools_cc README <https://github.com/eclipse-score/bazel-tools-cc/blob/main/README.md>`_ and an
     `example project <https://github.com/eclipse-score/bazel-tools-cc/tree/main/test>`_ 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 :ref:`logging daemon <logging_daemon>`.
+- Platform functionality was extended with `logging daemon <https://github.com/eclipse-score/logging>`_.
 
 
 S-CORE Platform