Use less specific language about DB fix version
What does this MR do?
To dovetail with the release post fix in gitlab-com/www-gitlab-com!124035 (merged), this merge request changes the upgrade notes to be less specific about which version the database migration problem in #408304 (closed) will be fixed. We originally thought it would be 15.11.1, but that's turned out to be a security-only patch release. It's probably 15.11.2 but we don't actually know that answer yet, so let's be vague rather than continually updating the info.
People who are involved with shepherding this fix to production: @jon_jenkins, @alexives, @bprescott_.
Evan, I'm comfortable with Alex doing a post-merge review here; I'd feel a lot better if we could get this out relatively quickly.
Related issues
- Related to Failure in update_major test (#408304 - closed)
- Related to Change patch info from 15.11.1 to ??? (gitlab-com/www-gitlab-com!124035 - merged)
Author's checklist
-
Optional. Consider taking the GitLab Technical Writing Fundamentals course. -
Follow the: -
If you're adding or changing the main heading of the page (H1), ensure that the product tier badge is added. -
If you are a GitLab team member, request a review based on: - The documentation page's metadata.
- The associated Technical Writer.
If you are a GitLab team member and only adding documentation, do not add any of the following labels:
~"frontend"
~"backend"
~"type::bug"
~"database"
These labels cause the MR to be added to code verification QA issues.
Reviewer's checklist
Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.
If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.
-
If the content requires it, ensure the information is reviewed by a subject matter expert. - Technical writer review items:
-
Ensure docs metadata is present and up-to-date. -
Ensure the appropriate labels are added to this MR. -
Ensure a release milestone is set. - If relevant to this MR, ensure content topic type principles are in use, including:
-
The headings should be something you'd do a Google search for. Instead of Default behavior
, say something likeDefault behavior when you close an issue
. -
The headings (other than the page title) should be active. Instead of Configuring GDK
, say something likeConfigure GDK
. -
Any task steps should be written as a numbered list. - If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
-
-
-
Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.
Merge request reports
Activity
changed milestone to %16.0
assigned to @aqualls
removed maintenancerefactor label
mentioned in issue #408304 (closed)
1 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. Documentation review
The following files require a review from a technical writer:
-
doc/update/index.md
(Link to current live version)
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.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger-
mentioned in merge request gitlab-com/www-gitlab-com!124035 (merged)
removed priority1 label
removed failurenew label
removed bugfunctional label
removed severity1 label
added docsfix maintenancerefactor typemaintenance labels and removed docsimprovement typebug labels
added Technical Writing Unplanned labels
added tw-weight3 twdoing labels
added docs-only label
mentioned in commit fdf026e2
added workflowstaging-canary label and removed workflowin dev label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
mentioned in issue technical-writing#800
added workflowpost-deploy-db-staging label and removed workflowproduction label
added workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label
mentioned in issue #408768 (closed)
added releasedcandidate label
added groupdatabase frameworks label and removed groupdatabase [DEPRECATED] label