Update status of namespace in URL path to Beta from Experiment
What does this MR do?
Update status of namespace in URL path to Beta from Experiment. This also include some explanation in the docs.
Changelog: other
Related issues
Author's checklist
-
Optional. Consider taking the GitLab Technical Writing Fundamentals course. -
Follow the: -
If you're adding a new page, add the product tier badge 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 %16.11
assigned to @ngala
added devopsplan sectiondev labels
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/pages/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.
Reviewer roulette
Category Reviewer Maintainer backend @rcobb
(UTC-7, 3 hours behind author)
@sgarg_gitlab
(UTC+5.5, 9.5 hours ahead of author)
frontend @dftian
(UTC-10, 6 hours behind author)
@himkp
(UTC+2, 6 hours ahead of author)
Please check reviewer's status!
Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger-
- Resolved by Phillip Wells
@kassio Can you please review this docs change. Thank you
requested review from @kassio
added docs-only label
mentioned in issue #17584 (closed)
- Resolved by Phillip Wells
removed review request for @kassio
requested review from @kassio
removed docs-only label
mentioned in issue #434370 (closed)
removed backend label
added pipeline:mr-approved label
- Resolved by Phillip Wells
@kassio
, 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.
- A deleted user
added backend label
E2E Test Result Summary
allure-report-publisher
generated test report!e2e-test-on-gdk:
test report for 6d53bb42expand test summary
+------------------------------------------------------------------+ | suites summary | +-------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-------------+--------+--------+---------+-------+-------+--------+ | Govern | 66 | 0 | 0 | 0 | 66 | ✅ | | Plan | 51 | 0 | 2 | 0 | 53 | ✅ | | Verify | 35 | 0 | 1 | 0 | 36 | ✅ | | Create | 83 | 0 | 9 | 0 | 92 | ✅ | | Package | 24 | 0 | 6 | 0 | 30 | ✅ | | Manage | 0 | 0 | 1 | 0 | 1 | ➖ | | Monitor | 7 | 0 | 0 | 0 | 7 | ✅ | | Data Stores | 31 | 0 | 0 | 0 | 31 | ✅ | | Analytics | 2 | 0 | 0 | 0 | 2 | ✅ | | Release | 5 | 0 | 0 | 0 | 5 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+ | Total | 304 | 0 | 19 | 0 | 323 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+
e2e-package-and-test:
test report for 6d53bb42expand test summary
+------------------------------------------------------------------+ | suites summary | +-------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-------------+--------+--------+---------+-------+-------+--------+ | Plan | 249 | 0 | 19 | 0 | 268 | ✅ | | Create | 152 | 0 | 21 | 2 | 173 | ✅ | | Govern | 6 | 0 | 0 | 0 | 6 | ✅ | | Monitor | 8 | 0 | 0 | 0 | 8 | ✅ | | Data Stores | 4 | 0 | 0 | 0 | 4 | ✅ | | Package | 0 | 0 | 2 | 0 | 2 | ➖ | +-------------+--------+--------+---------+-------+-------+--------+ | Total | 419 | 0 | 42 | 2 | 461 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+
- Resolved by Phillip Wells
@himkp Can you please perform maintainer review for frontend change? Thank you
Edited by Naman Jagdish Gala
requested review from @himkp
requested review from @nolith
removed review request for @nolith
requested review from @phillipwells
added Technical Writing docs-channel labels
- Resolved by Naman Jagdish Gala
- Resolved by Naman Jagdish Gala
- Resolved by Naman Jagdish Gala
- Resolved by Naman Jagdish Gala
- Resolved by Phillip Wells
@ngala I've left a couple suggestions for you here
Thanks!
removed review request for @phillipwells
requested review from @phillipwells
enabled an automatic merge when the pipeline for f078b48b succeeds
mentioned in commit 12252512
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-production label and removed workflowproduction label
added releasedcandidate label
mentioned in merge request kubitus-project/kubitus-installer!2945 (merged)
mentioned in merge request !151313 (merged)
added releasedpublished label and removed releasedcandidate label
added pipelinetier-3 label