Skip to content

Standard links correction: Release Mgt #104

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
aschemmel-tech merged 1 commit into from
Jul 8, 2025
Merged

Standard links correction: Release Mgt #104

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion process/process_areas/release_management/guidance/release_guideline.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Guideline
.. gd_guidl:: Release Management Guideline
:id: gd_guidl__rel_management
:status: valid
:complies: std_req__iso26262__management_64131, std_req__iso26262__management_64132, std_req__iso26262__management_64133
:complies: std_req__iso26262__management_64131, std_req__iso26262__management_64132, std_req__iso26262__management_64133, std_req__iso26262__management_64135

.. _workflow_release:

Expand Down
26 changes: 13 additions & 13 deletions process/process_areas/release_management/guidance/release_templates.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,16 +93,16 @@ Templates
:status: valid
:complies: std_req__iso26262__management_64131, std_req__iso26262__management_64132, std_req__iso26262__management_64133

Copy the below steps into the release ticket:

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 (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`
8. Merge PR and close this issue to complete the release
| Copy the below steps into the release ticket:
|
| 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 (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`
| 8. Merge PR and close this issue to complete the release