Edit deprecation for removal in GitLab 18.0
-
Please check this box if this contribution uses AI-generated content as outlined in the GitLab DCO & CLA.
What does this MR do?
As a follow up to: !144394 (merged), and to support !150710 (merged), update a deprecation notice with a more up-to-date plan.
Author's checklist
-
Optional. Consider taking the GitLab Technical Writing Fundamentals course. -
Follow the: -
If you're adding a new page, add the product availability details under the H1 topic title. -
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 %17.1
assigned to @eread
added pipelinetier-1 label
- Resolved by Russell Dickenson
@nrosandich This is what I had in mind for !150710 (comment 1908017708). WDYT?
added devopsgovern groupcompliance labels
requested review from @nrosandich
added sectionsec label
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/api/rest/deprecations.md
(Link to current live version) -
doc/update/deprecations.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-
requested review from @sam.figueroa
added pipeline:mr-approved label
- Resolved by Russell Dickenson
@nrosandich
, thanks for approving this merge request.This is the first time the merge request has been approved. To ensure we don't only run predictive pipelines, and we don't break
master
, a new pipeline will be started shortly.Please wait for the pipeline to start before resolving this discussion and set auto-merge for the new pipeline. See merging a merge request for more details.
added pipelinetier-3 label and removed pipelinetier-1 label
removed review request for @nrosandich
added 1059 commits
-
e811f5d5...4c8731d4 - 1058 commits from branch
master
- 9fdb2f26 - Move deprecation notice to REST API deprecation page
-
e811f5d5...4c8731d4 - 1058 commits from branch
requested review from @nrosandich
removed review request for @nrosandich
requested review from @rdickenson and removed review request for @sam.figueroa
enabled an automatic merge when all merge checks for 9fdb2f26 pass
- Resolved by Russell Dickenson
@sam.figueroa I've reviewed and approved this MR, and set it to auto-merge when the dependent [1] MR is merged.
[1] !150710 (merged)
removed review request for @rdickenson
mentioned in merge request !150710 (merged)
added 2477 commits
-
9fdb2f26...be99f5c3 - 2476 commits from branch
master
- ab6bc26b - Edit deprecation for removal in GitLab 18.0
-
9fdb2f26...be99f5c3 - 2476 commits from branch
added 942 commits
-
ab6bc26b...3388539e - 941 commits from branch
master
- 03cea00c - Edit deprecation for removal in GitLab 18.0
-
ab6bc26b...3388539e - 941 commits from branch
reset approvals from @rdickenson by pushing to the branch
requested review from @rdickenson
changed milestone to %17.2
added 413 commits
-
03cea00c...18bda5dd - 412 commits from branch
master
- a7bf3ada - Edit deprecation for removal in GitLab 18.0
-
03cea00c...18bda5dd - 412 commits from branch
mentioned in commit 5b3c074e
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
added workflowpost-deploy-db-staging label and removed workflowproduction label
added releasedcandidate label
added releasedpublished label and removed releasedcandidate label