Create 14.4 What's New entry
What does this MR do and why?
Creates the 14.4 what's new entry
Describe in detail what your merge request does and why.
Screenshots or screen recordings
These are strongly recommended to assist reviewers and reduce the time to merge your change.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Merge request reports
Activity
changed milestone to %14.4
added Pick into 14.4 documentation 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:
data/whats_new/2021102000001_14_04.yml
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
Dangerassigned to @adawar
requested review from @fseifoddini
@fseifoddini
, thanks for approving this merge request.This is the first time the merge request is approved. To ensure full test coverage, a new pipeline has been started.
For more info, please refer to the following links:
@a_akgun Heads up on this What's New entry - I am pulling it down locally to verify everything looks correct but would you mind doing a review and merging when you have a chance (assuming everything looks ok)?
assigned to @a_akgun
requested review from @a_akgun
assigned to @mkarampalas
- Resolved by Michael Karampalas
- Resolved by Alper Akgun
Unrelated to the current, why do we still show plans for self-managed and SaaS separately, after we deprecated silver/gold naming?
For example: I mean do we have features which are available on ultimate saas, and not on ultimate self-managed or vice versa?
https://about.gitlab.com/releases/2021/10/22/gitlab-14-4-released/
- Resolved by Michael Karampalas
mentioned in commit 7e66d89d
added workflowstaging-canary label
added workflowstaging label and removed workflowstaging-canary label
added workflowcanary label and removed workflowstaging label
added workflowproduction label and removed workflowcanary label
added typemaintenance label
picked the changes into the branch
14-4-stable-ee-patch-2
with commit 5435af9ementioned in commit 5435af9e
Automatically picked into !73919 (merged), will merge into
14-4-stable-ee
ready for14.4.2-ee
.removed Pick into 14.4 label
mentioned in merge request !73919 (merged)
added releasedcandidate label
added releasedpublished label and removed releasedcandidate label