Update broken-migration statement to say 15.11.3
Why is this change being made?
From this thread gitlab-org/gitlab#408304 (comment 1377478540) we now know the fix for Failure in update_major test (gitlab-org/gitlab#408304 - closed) is coming in GitLab 15.11.3, so let's update the part of the release post data/release_posts/15_11/upgrade-migration-broken.yml
(last updated in !124035 (merged)) to reflect that patch version number.
@alexives, @bprescott_, @jon_jenkins: as promised, staying on top of this issue until we get a fix out.
Related issues
- Related to Failure in update_major test (gitlab-org/gitlab#408304 - closed)
- Related to Post merge review of https://gitlab.com/gitlab-... (gitlab-org/gitlab#408768 - closed)
- Related to Update fix version in docs to 15.11.3 (gitlab-org/gitlab!120546 - merged) where I'm also updating the upgrade documentation
Author Checklist
-
Provided a concise title for this Merge Request (MR) -
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained by
section on the page being edited - If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
- The when to get approval handbook section explains the workflow in more detail
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR - If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.
Edited by Amy Qualls