Merge pull request #1060 from eclipse-score/aschemmel-tech-patch-1

docs: update config_management with links

Author: masc2023

docs/platform_management_plan/config_management.rst

@@ -53,21 +53,21 @@ Approach
 .. gd_guidl:: Configuration
    :id: gd_guidl__configuration
    :status: valid
-   :complies: std_req__iso26262__support_741, std_req__iso26262__support_743, std_req__iso26262__support_744, std_req__iso26262__support_745
+   :complies: std_req__iso26262__support_741, std_req__iso26262__support_742, std_req__iso26262__support_743, std_req__iso26262__support_744, std_req__iso26262__support_745, std_req__aspice_40__SUP-8-BP1, std_req__aspice_40__SUP-8-BP3, std_req__aspice_40__SUP-8-BP4, std_req__aspice_40__SUP-8-BP5, std_req__aspice_40__SUP-8-BP8
 
 
 Identification
 ^^^^^^^^^^^^^^
 
-Each work product is identified by its sphinx-needs Id, this includes documents identified as such (see :project documents list in :need:`doc__documentation_mgt_plan`).
+Each work product is identified by its sphinx-needs Id, this includes documents identified as such (see project documents list in :need:`doc__documentation_mgt_plan`).
 Spinx-needs checks for Id duplicates.
 The work products are stored in text or code files (these are identified by their filenames) within GitHub repositories.
 There is one `platform repository <https://GitHub.com/eclipse-score/score/>`_ and one repository for each module.
 
 For other artefacts these are either
 
 - files - are identified by their path/filename (and configured also in GitHub)
-- precompiled tools/binaries - bazel build configuration identifies those by their hash.
+- precompiled tools/binaries - bazel build configuration identifies those by their hash (see MODULE.bazel).
 - (external) tools/binaries to be built in S-CORE CI - bazel build configuration identifies those by their version.
 
 
@@ -112,7 +112,7 @@ The "remote" branch is not "local" to the developer but resides on the "remote"
 
 Baselines are created by using the GitHub "tag" function. The tag name shall correspond to
 the release branch name the tag is created, adding patch version and pre-release tag.
-See also release management (Todo: add link when `PR-578 <https://github.com/eclipse-score/score/pull/578>`_ is merged).
+See also :need:`doc__platform_release_management_plan`.
 
 Every change in the release repository is also taken over into the main branch. The module development team
 can decide how to ensure this (e.g. by development in main and cherrypick to release branch).

docs/process/process_areas/configuration_management/guidance/process_req.rst

@@ -18,7 +18,7 @@ Configuration Management Process Requirements
 .. gd_req:: Permanent Storage
    :id: gd_req__workproducts_storage
    :status: valid
-   :complies: std_req__iso26262__support_745
+   :complies: std_req__iso26262__support_745, std_req__aspice_40__SUP-8-BP8
 
    At least every platform release shall be stored permanently as a collection of text documents
    (docs and code) including the used OSS tooling outside of github servers.

docs/process/process_areas/release_management/guidance/release_templates.rst

@@ -18,7 +18,7 @@ Templates
 .. gd_temp:: Platform Release Note Template
    :id: gd_temp__rel__plat_rel_note
    :status: valid
-   :complies: std_req__iso26262__management_64134, std_req__iso26262__management_64135
+   :complies: std_req__iso26262__management_64134, std_req__iso26262__management_64135, std_req__aspice_40__SUP-8-BP7
 
    |  Platform Release Notes
    |  ======================
@@ -148,7 +148,7 @@ Release <add version number> for <platform/module_name>
 1. Link this issue to the correct milestone and assign to the technical lead
 2. Check respective Verification report on the release candidate's github tag
 3. Check bugfixes or justify failed tests
-4. Check the safety package completeness (supported by the safety manager)
+4. Check the safety package completeness (includes "valid" documents and work products status, supported by the safety manager)
 5. Create/update the release note (pull request to close this issue)
 6. Document safety manager's "recommendation to release" by asking his GitHub review approval of the release note
 7. Create the "release" in GitHub according to :need:`gd_guidl__rel_management`