Update release/docs to reflect new patch terminology
Patch releases have been repurposed to patches that include bug and security fixes, deprecating the term 'security release'. The release/docs
repository should be updated to account for this terminology update
-
Preparation gitlab-org/release/docs!707 (merged) -
Update the patch release readme gitlab-org/release/docs!708 (merged) -
Update patch release sections gitlab-org/release/docs!710 (merged) -
Update patch release manager file gitlab-org/release/docs!711 (merged) -
Update the security release readme gitlab-org/release/docs!714 (merged) -
Update the security release engineer readme gitlab-org/release/docs!716 (merged) -
Update the security release manager readme gitlab-org/release/docs!718 (merged) -
Update the security release quality readme gitlab-org/release/docs!719 (merged) -
Update the security release security engineer readme gitlab-org/release/docs!720 (merged) -
Replace the 'security release' terminology gitlab-org/release/docs!720 (merged) -
Ensure release manager documentation is up to date gitlab-org/release/docs!711 (merged) / gitlab-org/release/docs!718 (merged) -
Update links on dashboard gitlab-com/runbooks!7304 (merged) -
Update links on handbook gitlab-com/content-sites/handbook!5601 (merged) -
Update links on templates: bug and security gitlab-org/gitlab!152529 (merged) / gitlab-org/gitlab!151933 (merged) -
Update security/engineer.md
links on GitLab gitlab-com/content-sites/handbook!5600 (merged) -
Update release manager onboarding gitlab-org/release/tasks!111 (merged) -
Open follow-up to replace 'security release' with 'patch release' in release/docs #20212
Edited by Mayra Cabrera