Clarify release process
What does this MR do and why?
This MR clarifies the release process. It came out of the explanation here !206 (comment 1375462361).
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Merge request reports
Activity
assigned to @.luke
changed milestone to %16.0
added groupimport and integrate maintenancerefactor typemaintenance labels
added devopsmanage sectiondev labels
- Resolved by Lin Jen-Shin
Reviewer roulette
Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category and by a maintainer in all other categories.
To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.
To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.
Once you've decided who will review this merge request, mention them as you normally would! Danger does not automatically notify them for you.
Reviewer Maintainer Jennifer Li (
@jennli
) (UTC-7, 19 hours behind@.luke
)David Dieulivol (
@ddieulivol
) (UTC+2, 10 hours behind@.luke
)If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger- Resolved by Lin Jen-Shin
- Resolved by Lin Jen-Shin
@godfat-gitlab What do you think about this change to the
README.md
to try to clarify the process for contributors who are new?requested review from @godfat-gitlab
mentioned in issue gitlab-org/gitlab#408995 (closed)
@.luke Looks great to me, thank you so much for improving the documentation and formalizing the process!
added 3 commits
-
f732a414...9f947038 - 2 commits from branch
master
- 915a6229 - Clarify release process
-
f732a414...9f947038 - 2 commits from branch
enabled automatic add to merge train when the pipeline for e0a5dc2d succeeds
mentioned in commit d188ce67