Add documentation for the new patch release process
New documentation is required to account for the new process introduced on &968 (closed).
The documentation for developers should:
- It should state that merge requests should be opened against stable branches. This only applies for stable branches newer than 15.10
- Only one approval is required
- Package-and-test pipeline green status or Quality approval is required
- Maintainers can merge bug fixes
- QA guidance: package-and-test should be executed and if failures they should ask the SET counterpart for assistance. #2725 (comment 1260169794)
Basically, #2886 (closed) needs to be transformed into a patch release.
Documentation for release managers:
- Documentation for doing a patch release.
- Documentation to track failures on stable branches #2637 (closed)
- gitlab-org/release/docs!572 (merged)
#2902 (closed) contains all this information and should be moved into documentation.
Once documentation is updated https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/merge_request_templates/Stable%20Branch.md has to be updated as well
Edited by Mayra Cabrera