Update documentation for NFS support removal
What does this MR do?
As part of removal of support for NFS for Git repository data, update the documentation to make it clear that the removal of support has occured.
CC @axil just FYI.
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 %15.7
assigned to @eread
2 Warnings 09af16c0: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines. d20a4fdb: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines. 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/administration/gitaly/index.md
(Link to current live version) -
doc/administration/reference_architectures/10k_users.md
(Link to current live version) -
doc/administration/reference_architectures/25k_users.md
(Link to current live version) -
doc/administration/reference_architectures/2k_users.md
(Link to current live version) -
doc/administration/reference_architectures/3k_users.md
(Link to current live version) -
doc/administration/reference_architectures/50k_users.md
(Link to current live version) -
doc/administration/reference_architectures/5k_users.md
(Link to current live version) -
doc/administration/nfs.md
(Link to current live version) -
doc/update/removals.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-
- Resolved by Achilleas Pipinellis
@mjwood @andrashorvath Could you review?
requested review from @mjwood and @andrashorvath
@mjwood
, thanks for approving this merge request.This is the first time the merge request is approved. To ensure full test coverage, a new pipeline will be started shortly.
For more info, please refer to the following links:
- Resolved by Achilleas Pipinellis
- Resolved by Achilleas Pipinellis
added sectioncore platform label
added 342 commits
-
c3ecc8a8...d5c7c2ca - 340 commits from branch
master
- de7e7902 - Update documentation for NFS support removal
- 5ab04785 - Gitaly with NFS, not Gitaly and NFS, are not supported
-
c3ecc8a8...d5c7c2ca - 340 commits from branch
assigned to @axil and @grantyoung
unassigned @axil
added 1800 commits
-
5ab04785...5a7674cb - 1799 commits from branch
master
- 4503f43a - Update documentation for NFS support removal
-
5ab04785...5a7674cb - 1799 commits from branch
- Resolved by Evan Read
- Resolved by Evan Read
- Resolved by Evan Read
- Resolved by Evan Read
- Resolved by Evan Read
added 266 commits
-
4503f43a...8716953e - 264 commits from branch
master
- 810f141f - Update documentation for NFS support removal
- d20a4fdb - Further updates from review
-
4503f43a...8716953e - 264 commits from branch
requested review from @grantyoung
requested review from @axil
mentioned in commit 4d59dae4
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 releasedcandidate label
added releasedpublished label and removed releasedcandidate label