Skip to content

Prepare 11.5 RC6 release

Cindy Pallares 🦉 requested to merge 11-5-stable-prepare-rc6 into 11-5-stable

Main release issue: gitlab-org/release/tasks#510 (closed)

Summary

This MR prepares 11-5-stable for %11.5 (RC6) by merging 11-5-stable-prepare-rc6 into 11-5-stable.

Before the 7th

Merge master into the preparation branch

After the 7th

MR Filter for ~"Pick into 11.5" MRs

https://gitlab.com/gitlab-org/gitlab-ce/merge_requests?label_name%5B%5D=Pick+into+11.5&scope=all&state=merged

Note to leave in MRs

Picked into https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/MERGE_REQUEST_ID, will merge into `11-5-stable` ready for `11.5 RC6`

/unlabel ~"Pick into 11.5"

Steps

  1. Cherry-pick commits into this MR using the link for ~"Pick into 11.5" above.

    • This can be done by checking out 11-5-stable-prepare-rc6 locally and using git cherry-pick -m1 MERGE_COMMIT_SHA
    • Note: The quickest way to check the MERGE_COMMIT_SHA is to go the Discussion tab in the Merge Request. The merge commit SHA will be visible right before the comment of it being merged. Sometimes the merge commit SHA will not be available in the Discussion tab, in those cases you have to look for it in the commits tab for master

  2. Push changes every so often and verify that the MR has been included

  3. Leave a note in the MR so others can easily see that it is on track to be included in a release.

    • Remove the ~"Pick into 11.5" label.

  4. If there are any conflicts while picking MRs then attempt to resolve them; otherwise, create a new MR against the 11-5-stable-prepare-rc6 branch and assign it to the author of the conflicting files.

  5. Once this MR is green merge it to stable, preferably with a manual fast-forward merge to minimize waiting time, as described in Merging preparation MRs into stable

Checklist

  • Add changes into the preparation branches:

    • Before the 7th: Master has been merged into the preparation branch
    • After the 7th: Changes marked ~"Pick into 11.5" have been picked

  • Conflicts resolved

  • No new commits have introduced directly to the stable branch while this MR was in progress. If there are, ensure these are merged into EE and check for a green pipeline after merging this MR.

Edited by Steve Xuereb

Merge request reports