Refine what means latest version of gitlab
What does this MR do?
Correct the wording around the latest version of GitLab
.
The upgrade plan for PostgreSQL currently asks users to make sure they run the latest version of GitLab
.
In case of an GitLab upgrade from 13 to 14, users need to update to the latest GitLab version in the 13.x branch (13.12.15 at the moment), then need to upgrade PostgreSQL, which states be sure that you’re running the latest version of GitLab
. The latest version is 14.x.
That's confusing and could lead customer to feel they have to first upgrade GitLab to 14.x then upgrade PostgreSQL, as seen on this ZD ticket: internal link.
Related issues
Author's checklist
-
Consider taking the GitLab Technical Writing Fundamentals course -
Follow the: -
Ensure that the product tier badge is added to topic's h1
. -
Request a review based on: - The documentation page's metadata.
- The associated Technical Writer.
If you are only adding documentation, do not add any of the following labels:
~"feature"
~"frontend"
~"backend"
~"bug"
~"database"
These labels cause the MR to be added to code verification QA issues.
Review 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 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. - 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 above reviews. Maintainer's review can occur before or after a technical writer review. -
Ensure a release milestone is set.