Audit preparation: Release Mgt

[aschemmel-tech]

"not started" topics:

• availability of confirmation measure reports - https://eclipse-score.github.io/process_description/main/process_areas/release_management/guidance/release_guideline.html states the safety package has to be available and complete (which includes the Confirmation measure reports)

Actions and Deviations:

• Action_23: It shall be defined, to which release (major release, or patch release) the delta needs to be shown. The originating release tag needs to be documented. - see https://eclipse-score.github.io/process_description/main/process_areas/release_management/guidance/release_templates.html#gd_temp__rel__plat_rel_note and https://eclipse-score.github.io/process_description/main/folder_templates/modules/module_name/docs/release/release_note.html#doc__module_name_release_note
• Action_24: The module Verification report(s) shall be referenced. - same links as Action_23 above
• Action_25: The Safety Package (as part of the users’ Safety Case) shall be prepared. - see "Release Preparation" in https://eclipse-score.github.io/process_description/main/process_areas/release_management/guidance/release_guideline.html#gd_guidl__rel_management
• Action_26: It needs to be described, how the Project Management circle “approves” the release with “signature”. (it was discussed that this is a tick mark in the release ticket, and that this tick with a clear allocation to a person is equivalent to a signature). - see "Release Execution" in https://eclipse-score.github.io/process_description/main/process_areas/release_management/guidance/release_guideline.html plus disclaimer in https://eclipse-score.github.io/process_description/main/process_areas/release_management/guidance/release_templates.html