Audit preparation: Config Mgt

[aschemmel-tech]

"not started" topics:

• 7.4.2 meeting QM standard - see links in https://eclipse-score.github.io/process_description/main/process_areas/configuration_management/guidance/configuration_templates.html
• 7.4.3 baseline - see https://eclipse-score.github.io/process_description/main/process_areas/configuration_management/guidance/configuration_templates.html#branches-and-baselines
• 7.4.4 strategy - see https://eclipse-score.github.io/process_description/main/process_areas/configuration_management/guidance/configuration_templates.html#objectives-and-scope
• 7.4.5 lifecycle - see https://eclipse-score.github.io/process_description/main/process_areas/configuration_management/guidance/configuration_templates.html#lifecycle

Actions and Deviations:

• Deviation_15: There is no description for the baselining process which includes several GitHub repositories. - see https://eclipse-score.github.io/score/main/platform_management_plan/config_management.html#branches-and-baselines defining the sequence of releases in the repos.
• Deviation_16: It remains unclear how the baselines, caused by the needs of different companies, are controlled. Companies might require changes of an Eclipse baseline for their SOP. Is it really realistic that changes are made in components where the component owner is not part of the specific company (key message: BMW would never change a Vector delivery)? - see https://eclipse-score.github.io/score/main/platform_management_plan/project_management.html#releases-and-milestones - every user has the possibility to fork.