Change Management ML3

Epic Description

Get the Change Management from ML2 to ML3

• First the gaps in the process according to the definition in https://eclipse-score.github.io/process_description/main/ have to be documented in below list

  • deployment of process in one S-CORE module/platform repo, all documents are valid
    score, generic issue templates rolled-out, example https://github.com/orgs/eclipse-score/projects/4/views/7, existing examples
    https://github.com/orgs/eclipse-score/projects/4, https://github.com/eclipse-score/score/issues/2752, https://github.com/eclipse-score/score/issues/2751

    • baselibs, generic issue templates implemented, no examples yet
    • baselibs_rust, not yet implemented, delete local templates PR not merged yet
    • communication, not yet implemented, not yet implemented, delete local templates PR not merged yet
    • config_management, not yet implemented, not yet implemented, delete local templates PR not merged yet
    • feo, generic issue templates implemented, no examples yet
    • kyron, not yet implemented, not yet implemented, delete local templates PR not merged yet
    • lifecycle, generic issue templates implemented, no examples yet
    • ogging, generic issue templates implemented, no examples yet
    • orchestrator, not yet implemented, not yet implemented, delete local templates PR not done yet
    • persistency, generic issue templates implemented, no examples yet
    • scrample, not yet implemented, not yet implemented, delete local templates PR not done yet
    • process_description, generic issue templates implemented
    • Which other repos are from interest, e.g.
    • nlohmann_json, not yet implemented, not yet implemented, delete local templates PR not done yet
    • score_crates, generic issue templates implemented, no examples yet

  • process requirements prio 1&2 "automation" are implemented in tooling

    • gd_req__change_attr_title, Prio1, Part of Issue Type
    • gd_req__change_attr_impact_description, Prio1, Part of Issue Type
    • gd_req__change_attr_impact_safety, Prio 1, Part of Issue Type, only partly relevant for doc-as-code
    • gd_req__change_attr_impact_security, Prio 2, Part of Issue Type, only partly relevant for doc-as-code
    • gd_req__change_attr_types, Prio 1, Issue Type itself, and part, not relevant for doc-as-code
    • gd_req__change_attr_affected_wp, Part of Issue Type, Done by version changes, automated by Doc-as-Code
    • gd_req__change_attr_milestone, Part of Issue
    • gd_req__change_attr_mandatory, Covered per Issue Type, not relevant for doc-as-code
    • gd_req__change_tool_impact_analysis, Prio 3, Doc-as-Code by version check

    Implemented e.g. in https://github.com/eclipse-score/.github/blob/main/.github/ISSUE_TEMPLATE/1a_FeatureRequest.yml,

  • respective tool evaluation done

    • Doc-as-code with sphinx-needs feature, Tool Evaluation done, Tool Qualification in Work
      https://eclipse-score.github.io/score/main/score_tools/tools_documentation/doc_as_code.html#doc_tool__doc_as_code
      https://eclipse-score.github.io/docs-as-code/pr-831/internals/requirements/tool_qualification_example.html

  • Safety Audit passed (no open deviations/actions)

    • https://github.com/eclipse-score/process_description/issues/567
    • Deviation_17: The Impact Analysis on Element Level is not defined by the process definition. It shall be identified which ISO 26262 work products are affected by the change. All identified WPs with version, checked by Doc-as-Code

Acceptance Criteria (DoD)

all identified gaps have been resolved