Adjust stable branches configuration on the GitLab project
Currently GitLab stable branches can only be modified by release managers, as part of &828 (closed), we need to open up these branches to be modified by the maintainers of the GitLab project.
These branches are used as a source for self-managed releases, and because of it, their integrity should be guaranteed. Before opening these branches to the maintainers of the project we should:
-
Ensure merge requests targeting stable branches run a full set of tests: -
FOSS -
EE -
End-To-End tests (https://docs.gitlab.com/ee/development/testing_guide/end_to_end/)
-
- [-]
If a new set of tests needs to be included it is likely the pipelines on stable branches will take longer, make sure to notify Release Managers about it.No tests were identified that needed to be added to stable branches. -
Merge requests targeting stable branches should only be merged if it's green and if it has all the approvals. -
Merge requests should use "Pipeline for merged results" (same as the default branch) -
Make use of review-apps - This is not a requirement and can be done in a follow up. It may be useful for &837 (closed)
Edited by Steve Abrams