Improvement: Document Release Management Process #313
Comments
|
kroehnd
added a commit
to mercedes-benz/score
that referenced
this issue
Mar 7, 2025
Added initial release managmenet process description. Edited process_areas index.rst to point to new release_management process. Moved workproducts from general area to new release_management process Fixed gitlint issues, added missing Copyright header. Resolves: eclipse-score#313
kroehnd
added a commit
to mercedes-benz/score
that referenced
this issue
Mar 7, 2025
- Edited process_areas index.rst to point to new release_management process. - Moved workproducts from general area to new release_management process. - Fixed gitlint error - Added missing Copyright header Resolves: eclipse-score#313
kroehnd
added a commit
to mercedes-benz/score
that referenced
this issue
Mar 7, 2025
Added initial release managmenet process description. Edited process_areas index.rst to point to new release_management process. Moved workproducts from general area to new release_management process Fixed gitlint issues, added missing Copyright header. Resolves: eclipse-score#313
kroehnd
added a commit
to mercedes-benz/score
that referenced
this issue
Mar 12, 2025
// Fixes based on comments TODO: text and marked with a thumbs up - Added proposal for the git branching strategy. - Mentioned the possibility to justify failed test cases. - Added Versioning Policy Chapter. - Fixed typo in release concept. - Added link to detailed overview of responsibilities. - Fixed indent in release workflow. - Added wp__module_sw_verification_report to inputs. - Replaced module safety case with platform safety case. - Adapted module safety case to use platform safety case. - Added wp__platform_sw_verification_report to inputs. - Added wp__platform_mgmt and wp__issue_track_system to inputs. - Changed status to valid for work products. - Adapted inputs and separated outputs list. - Slight rework of wording to capture "feature requests". - Added release note mention for each module. - Changed wording from Version to Release Tag and added hash. - Adapted wording to refer to tech lead circle instead of platform release manager. - Changed wording to "publish within Eclipse SDV". - Mentioned tech lead circle for periodic meetings. - Adjusted template to mention safety in known issues. Resolves: eclipse-score#313
|
@aschemmel-tech can you take over the ticket? @kroehnd is on leave until mid mai. |
|
to be ready for audit on May-12, I will take over the rework. |
aschemmel-tech
added a commit
that referenced
this issue
Apr 30, 2025
Ref: resolves #313 Signed-off-by: aschemmel-tech <aschemmel_job@arcor.de>
aschemmel-tech
added a commit
that referenced
this issue
Apr 30, 2025
Ref: resolves #313 Signed-off-by: aschemmel-tech <aschemmel_job@arcor.de>
aschemmel-tech
added a commit
that referenced
this issue
May 9, 2025
Ref: closes #313 Signed-off-by: aschemmel-tech <aschemmel_job@arcor.de>
aschemmel-tech
added a commit
that referenced
this issue
May 9, 2025
Ref: closes #313 Signed-off-by: aschemmel-tech <aschemmel_job@arcor.de>
PandaeDo
pushed a commit
to qorix-group/score
that referenced
this issue
May 23, 2025
Ref: closes eclipse-score#313 Signed-off-by: aschemmel-tech <aschemmel_job@arcor.de>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Important
Make sure to link this issue with the PR for your improvement.
Document in score repository (until the process_description repo is available)
Create documentation according to "template":
https://github.com/eclipse-score/process_description/blob/main/requirements_engineering/index.rst
Prepare presentation in audit session
The text was updated successfully, but these errors were encountered: