Geo Upgrade warning for 14.9
What does this MR do and why?
Describe in detail what your merge request does and why.
Incident discovered ahead of release. This creates documentation to address the isse.
Screenshots or screen recordings
These are strongly recommended to assist reviewers and reduce the time to merge your change.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
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
added groupgeo label
requested review from @nhxnguyen, @vsizov, and @axil
assigned to @fzimmer
marked the checklist item I have evaluated the MR acceptance checklist for this MR. as completed
added Pick into 14.9 label
2 Messages CHANGELOG missing: If you want to create a changelog entry for GitLab FOSS, add the
Changelog
trailer to the commit message you want to add to the changelog.If you want to create a changelog entry for GitLab EE, also add the
EE: true
trailer to your commit message.If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.
This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge. If needed, you can retry the
danger-review
job that generated this comment.Documentation review
The following files require a review from a technical writer:
doc/administration/geo/replication/version_specific_updates.md
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.md
files that you've changed. The first few lines of each*.md
file identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
Generated by
DangerA P2 bug was uncovered a couple of hours ago and this here adjusts the release post with guidance for impacted customers
changed milestone to %14.9
@axil This should be ready to merge.
- Resolved by Achilleas Pipinellis
- Resolved by Achilleas Pipinellis
enabled an automatic merge when the pipeline for f6ecc262 succeeds
mentioned in commit 7867bc07
added workflowstaging-canary label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
picked the changes into the branch
14-9-stable-ee-patch-1
with commit 67863a43Automatically picked into !83388 (merged), will merge into
14-9-stable-ee
ready for14.9.1-ee
.removed Pick into 14.9 label
mentioned in commit 67863a43
mentioned in merge request !83388 (merged)
added releasedcandidate label
added releasedpublished label and removed releasedcandidate label