Release post - GitLab 11.4

Review Apps: https://release-11-4.about.gitlab.com/2018/10/22/gitlab-11-4-released/

Release post:

• Intro: https://gitlab.com/gitlab-com/www-gitlab-com/blob/release-11-4/source/posts/2018-10-22-gitlab-11-4-released.html.md
• Items: https://gitlab.com/gitlab-com/www-gitlab-com/blob/release-11-4/data/release_posts/2018_10_22_gitlab_11_4_released.yml
• Images: https://gitlab.com/gitlab-com/www-gitlab-com/tree/release-11-4/source/images/11_4

Related files:

• Features YAML link: https://gitlab.com/gitlab-com/www-gitlab-com/blob/release-11-4/data/features.yml
• Home page banner: https://gitlab.com/gitlab-com/www-gitlab-com/blob/release-11-4/source/includes/hello-bar.html.haml
• MVPs: https://gitlab.com/gitlab-com/www-gitlab-com/blob/release-11-4/data/mvps.yml

Handbook references:

• Blog handbook: https://about.gitlab.com/handbook/marketing/blog/
• Release post handbook: https://about.gitlab.com/handbook/marketing/blog/release-posts/
• Markdown guide: https://about.gitlab.com/handbook/product/technical-writing/markdown-guide/

People:

• Release Post Managers: https://about.gitlab.com/handbook/marketing/blog/release-posts/managers/
• Release Managers: https://about.gitlab.com/release-managers/

Release post manager	Tech writer	Copyedit	Messaging Lead	Social
@jramsay	@eread	xx	@johnjeremiah	xx

General contributions

Due date: 2018-10-12 (6th working day before the 22nd)

All contributions added by team members, collaborators, and Product Managers (PMs).

Author's checklist

Due date: 2018-10-12 (6th working day before the 22nd) - @jramsay

The PM leading the post is responsible for adding and checking the following items:

• Label MR: ~"blog post" release release post ~P1
• Assign the MR to yourself
• Add milestone
• Update the links and due dates in this MR description
• Make sure the blog post initial files, as well as this MR template contain the latest templates
• Add authorship (author's data)
• Ask the Marketing reviewer to add the introduction
• Add MVP (feature block)
• Add MVP to data/mvps.yml
• Add cover image (image_title) (scaled and compressed)
• Add social sharing image (twitter_image) (scaled and compressed)
• Make sure all feature descriptions are positive and cheerful
• Make sure all features listed in the direction page are included in the post
• Mention the release managers to remind them to add the upgrade barometer section
• Mention the team leads to remind them to add the performance improvements: Yorick, Douwe, Sean, Remy, Stan, Kamil, Tim Z., Clement, Andre
• Ping @atflowers and @aoetama to add the Release Radar webcast link
• Make sure Upgrade barometer is in
• Check which one is the top feature (with Job and William)
• Check if deprecations are included
• Alert people one working day before each due date (post a comment to #release-post Slack channel)
• Remove remaining template sections
• Make sure all images (png, jpg, and gifs) are smaller than 300 KB each
• Run the release post through an automated spell and grammar check
• Perform the content review

Recurring blocks

Due date: 2018-10-12 (6th working day before the 22nd)

The following sections are always present, and managed by the PM or Eng lead owning the related area:

• Add GitLab Runner improvements: Fabio
• Add Omnibus improvements: Joshua
• Add Mattermost update to the Omnibus improvements section: Victor
• Add Performance improvements: Douwe, Sean, Kamil, Yorick, Tim

Feature blocks

Due date: 2018-10-12 (6th working day before the 22nd)

The Product Managers are responsible for adding their feature blocks to the release post by the due date for general contributions. PMs are also responsible for adding any notable Community Contributions.

PMs: please check your box only when all your features and deprecations were added with completion (documentation links, images, etc). Pls don't check if there are still things missing.

• Andreas (@akaemmerle)
• Daniel (@danielgruesso)
• Fabio (@bikebilly)
• James (@jramsay)
• Jason (@jlenny)
• Jeremy (@jeremy_)
• Joshua (@joshlambert)
• Victor (@victorwu)

Tip: make your own checklist:

• Primary features
• Improvements (secondary features)
• Deprecations
• Documentation updated
• Documentation links added to the post
• Community contributions
• Illustrations added to the post (compressed)
• Update features.yml (with accompanying screenshots)

Review

Ideally, complete the review until the 4th working day before the 22nd, so that the 3rd and the 2nd working day before the release could be left for fixes and small improvements.

Content review

Due date: 2018-10-15 (5th working day before the 22nd)

Performed by the author of the post: @jramsay

• Label MR: ~"blog post" release review-in-progress
• Check all comments in the thread (make sure no contribution was left behind)
• Check Features' names
• Check Features' availability (Core, Starter, Premium, Ultimate badges)
• Check Documentation links (all feature blocks contain documentation_link)
• Make sure documentation_link links to feature webpages when available
• Update home page bannersource/includes/hello-bar.html.haml
• Features were added to data/features.yml (with accompanying screenshots)
• Check all images size < 300KB (compress them all with TinyPNG or similar tool)
• Pull master, resolve any conflicts
• Make sure all discussions in the thread are resolved
• Mention Mark Pundsack to remind him to review
• Assign the MR to the next reviewer (structural check)
• Lock features.yml with File Locking on the 21st

Structural check

Due date: 2018-10-17 (3rd working day before the 22nd)

Performed by technical writers: @eread

• 1. Structural check
• Add the label review-structure
• Check frontmatter (entries, syntax)
• Check image_title and twitter_image
• Check image shadow applied correctly: {image_noshadow: true} when an image already has shadow
• Videos/iframes wrapped in <figure> tags (responsiveness)
• Wrap text
• Check headers in sentence case
• Check feature and product names in capital case
• Check if images are harmonic/consistent
• Add/check cover img reference (at the end of the post)
• Columns (content balance between the columns)
• Meaningful links (SEO)
• Badges consistency (applied to all headings)
• Double check documentation updates
• Check documentation links (point to /ee/, not to /ce/)
• Check about.gitlab.com links: relative URLs
• Check the anchor links in the intro
• Remove any remaining instructions
• Remove HTML comments
• Run deadlink checker
• Pull master
• Update release template with any changes (if necessary)
• Post a comment in the #general channel linking to the review app + MR reminding the team to take a look at the RP and report any problems in the #release-post channel. (Do NOT ping @all or @channel)
• Remove the label review-structure
• Assign the MR to the next reviewer (copyedit)

Further reviews

Due date: 2018-10-18 (2nd working day before the 22nd)

• Copyedit (content team): @erica
  • Title
  • Description
  • Intro
  • Grammar, spelling, clearness (body)
  • Homepage Blurb
  • Tweet social sharing text (for Twitter, FB, and LinkedIn)
  • Assign the MR to the next reviewer (marketing)
• Marketing review (PMMs - messaging lead): @johnjeremiah
  • Write the introduction (by the 6th day before the 22nd)
  • Check/copyedit feature blocks
  • Check/copyedit features.yml
  • Check/copyedit homepage blurb
  • Check/copyedit social sharing text
  • Mention Job for final check
  • Remove the label review-in-progress
  • Assign the MR back to the author

Merge it

The author of the post is responsible for merging the MR and following up with possible adjustments/fixes.

Last check before merging

• Read the important notes below
• Mention @matteeyah to remind him to send the swag pack to the MVP
• Check if all the anchor links in the intro are working
• Check if there are no broken links
• Pull master and fix any conflicts
• Check if there isn't any alert on Slack's #release-post and #general channels
• Check if there isn't any alert on this MR thread
• Check if the tweet copy is ready and someone is ready to share on social media
• Ask the release managers to ping you when the packs are publicly available (and GitLab.com is up and running on the release version)
• Unlock features.yml just before merging
• Merge the MR
• Wait for the pipeline
• Check the look on social media with Twitter Card Validator and Facebook Debugger
• Share on social media

Important notes

• The post is to be merged on the 22nd at 15:00 UTC and as soon as GitLab.com is up and running on the new release version, and all packages are publicly available. Not before.
• The usual release time is 15:00 UTC but it varies according to the deployment. If something comes up and delays the release, the release post will be delayed with the release.
• Coordinate the timing with the release managers. Ask them to keep you in the loop.
• After merging, wait a few minutes to see if no one spot an error (usually posted in #general), then share on Twitter, Facebook, and LinkedIn, or make sure someone (Emily vH, JJ, Marcia) does.
• Keep an eye on Slack and in the blog post comments for a few hours to make sure no one found anything that should be fixed

data/release_posts/2018_10_22_gitlab_11_4_released.yml

 features:
 # TOP FEATURE
   top:
-    - name: "Merge request reviews"
+    - name: "Merge Request Reviews"
       available_in: [premium, ultimate]
       documentation_link: 'https://docs.gitlab.com/ee/user/discussions/index.html'
       image_url: '/images/11_4/batch-comments.png'
@@ -17,7 +17,7 @@ features:
         comments unnecessary. The end result is that the merge request author
         gets a slew of notifications and has to sort them out one by one.
-        With this release, we are introducing merge request reviews. This will
+        With this release, we are introducing Merge Request Reviews. This will
         allow a reviewer to draft as many code comments in a merge requests as they
         wish, make sure they are all consistent, and then submit them all
         as a single action. Since the drafts are saved to GitLab, a reviewer can
@@ -138,10 +138,10 @@ features:
       issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/19232'
       description: |
         A popularly requested feature, we're proud to now offer the
-        ability within the `.gitlab-ci.yml` to use only/except rules for jobs
+        ability within the `.gitlab-ci.yml` to use `only`/`except` rules for jobs
         based on when modifications occur to a specific file or path (glob).
-        This will allow more control for users whose repos contain different
+        This will allow more control for users whose repositories contain different
         kinds of assets or builds, ensuring only the appropriate steps are
         executed for the kinds of changes that were committed, speeding up
         overall pipeline execution.
@@ -223,7 +223,7 @@ features:
       team: configure
       issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/48004'
       description: |
-        Leveraging Auto DevOps to automatically detect, build, test, deploy, and monitor your application
+        Using Auto DevOps to automatically detect, build, test, deploy, and monitor your application
         just got more powerful. Starting in 11.4, Auto DevOps now provides the ability to initialize or
         migrate PostgreSQL databases in your project.
@@ -270,6 +270,22 @@ features:
         of work, versus those that are toward the final stages of review before
         merge.
+    - name: "Highlight <code>@mentions</code> for yourself distinctly"
+      available_in: [core, starter, premium, ultimate]
+      documentation_link: 'https://docs.gitlab.com/ee/user/project/issues/issues_functionalities.html#13-mentions'
+      image_url: '/images/11_4/highlight-yourself-distinct.png'
+      reporter: victorwu
+      team: plan
+      issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/49036'
+      description: |
+        When collaborating in a long discussion in an issue or merge request, often
+        many users are involved, making it difficult to quickly at a glance, see
+        comments that are directed at you.
+
+        With this release, `@mentions` for yourself (i.e. the current user), are highlighted
+        in a different color, allowing you to easily see which comments involve you,
+        helping you focus on them quickly.
+
     - name: "Click to insert Markdown table and link"
       available_in: [core, starter, premium, ultimate]
       documentation_link: 'https://docs.gitlab.com/ee/user/markdown.html'
@@ -278,7 +294,7 @@ features:
       team: plan
       issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/29788'
       description: |
-        GitLab supports GitLab-flavored Markdown (GFM) in most places throughout
+        GitLab supports GitLab Flavored Markdown (GFM) in most places throughout
         GitLab where you enter text, providing the power of rich formatting with
         a simple syntax. In particular, you can create tables in GFM. Previously,
         this was painful to use, especially for large tables, since you had to type
@@ -299,22 +315,6 @@ features:
         Thank you [Jan Beckmann](https://gitlab.com/kingjan1999) for the URL link contribution!
-    - name: "Highlight <code>@mentions</code> for yourself distinctly"
-      available_in: [core, starter, premium, ultimate]
-      documentation_link: 'https://docs.gitlab.com/ee/user/project/issues/issues_functionalities.html#13-mentions'
-      image_url: '/images/11_4/highlight-yourself-distinct.png'
-      reporter: victorwu
-      team: plan
-      issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/49036'
-      description: |
-        When collaborating in a long discussion in an issue or merge request, often
-        many users are involved, making it difficult to quickly at a glance, see
-        comments that are directed at you.
-
-        With this release, `@mentions` for yourself (i.e. the current user), are highlighted
-        in a different color, allowing you to easily see which comments involve you,
-        helping you focus on them quickly.
-
     - name: "Include new issues created in Burndown Chart"
       available_in: [starter, premium, ultimate]
       documentation_link: 'https://docs.gitlab.com/ee/user/project/milestones/burndown_charts.html'
@@ -323,15 +323,15 @@ features:
       team: plan
       issue_url: 'https://gitlab.com/gitlab-org/gitlab-ee/issues/6174'
       description: |
-        Burndown charts help teams track work, as it progresses throughout a milestone.
+        Burndown Charts help teams track work, as it progresses throughout a milestone.
         Usually, the scope of work is decided and agreed on before the milestone
         begins. But occasionally, there will be important exceptions to the rule,
         (such as an emergency bug or security fix) and new scope needs to be included,
         in the form of new issues.
-        With this release, the burndown chart now accounts for these
+        With this release, burndown charts now accounts for these
         new issues that are created in the middle of a milestone, resulting in an
-        uptick of the line in a burndown chart.
+        uptick of its line.
     - name: "Expanded weight values in issues API"
       available_in: [starter, premium, ultimate]
@@ -402,6 +402,7 @@ features:
       available_in: [core, starter, premium, ultimate]
       documentation_link: 'https://docs.gitlab.com/ee/user/search/#projects'
       image_url: '/images/11_4/explore-projects-by-stars.png'
+      image_noshadow: true
       reporter: akaemmerle
       team: manage
       issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/47203'
@@ -426,7 +427,7 @@ features:
         With GitLab 11.4, we introduce an additional absolute measure by showing
         a new percentage value for each relevant code language shown. This provides
-        a more quantative touch point of your project's technology stack.
+        a more quantitative view of your project's technology stack.
         Thank you for this contribution, [Johann Hubert Sonntagbauer](https://gitlab.com/johann.sonntagbauer)!
@@ -438,7 +439,7 @@ features:
       team: manage
       issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/47963'
       description: |
-        Two-factor authentification is a de facto standard for signing up for any relevant web-based
+        Two-factor authentication is a de facto standard for signing up for any relevant web-based
         application. At GitLab we understand and take this seriously. Whenever you set up a two-factor
         authentication initially, we provide limited recovery codes that allow you to regain access
         to your account as a fallback.
@@ -476,6 +477,20 @@ features:
         improve this behavior by resolving [#3605](https://gitlab.com/gitlab-org/gitlab-runner/issues/3605) in
         our next release.
+    - name: "Skip Auto DevOps jobs based on feature availability"
+      available_in: [core, starter, premium, ultimate]
+      documentation_link: 'https://docs.gitlab.com/ee/topics/autodevops/'
+      reporter: danielgruesso
+      team: configure
+      issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/48399'
+      description: |
+        Starting in 11.4 Auto DevOps will now evaluate the plan (GitLab.com) or tier (self-managed)
+        for the instance in which it's running in order to determine which jobs to skip. This will
+        result in faster Auto DevOps pipeline when certain features are not in use.
+
+        This will not only save you time but will also result in a cleaner view of Auto DevOps pipeline,
+        showing you only the relevant jobs for your project.
+
     - name: "Allow pipelines to schedule delayed job runs"
       available_in: [core, starter, premium, ultimate]
       documentation_link: 'https://docs.gitlab.com/ee/ci/yaml/README.html#when-delayed'
@@ -491,20 +506,6 @@ features:
         example, when implementing timed incremental rollouts, or any
         other delays needed after performing some other action.
-    - name: "Skip Auto DevOps jobs based on feature availability"
-      available_in: [core, starter, premium, ultimate]
-      documentation_link: 'https://docs.gitlab.com/ee/topics/autodevops/'
-      reporter: danielgruesso
-      team: configure
-      issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/48399'
-      description: |
-        Starting in 11.4 Auto DevOps will now evaluate the plan (GitLab.com) or tier (self-managed)
-        for the instance in which it's running in order to determine which jobs to skip. This will
-        result in faster Auto DevOps pipeline when certain features are not in use.
-
-        This will not only save you time but will also result in a cleaner view of Auto DevOps pipeline,
-        showing you only the relevant jobs for your project.
-
     - name: "Interactive runbooks with Nurtch and JupyterHub"
       available_in: [core, starter, premium, ultimate]
       documentation_link: 'https://docs.gitlab.com/ee/user/project/clusters/#installing-applications'
@@ -574,6 +575,27 @@ features:
         globally run `git config --global protocol.version=2`. Git protocol v2
         over SSH is not yet enabled on GitLab.com and must be enabled manually.
+    - name: "Geo UX improvements in Admin Area"
+      available_in: [premium, ultimate]
+      gitlab_com: false
+      documentation_link: 'https://docs.gitlab.com/ee/administration/geo/replication/configuration.html'
+      image_url: '/images/11_4/geo_admin_area_improvements.png'
+      reporter: akaemmerle
+      team: geo
+      issue_url: 'https://gitlab.com/gitlab-org/gitlab-ee/issues/7126'
+      description: |
+        As a Geo admin, keeping an overview of your secondary nodes setup and the synchronization
+        state is crucial when working with distributed teams.
+
+        With GitLab 11.4, we improve the Geo-related Admin Area settings by improving and showing even
+        more synchronization and verification details in the user interface. On your primary node, a
+        new button "Open projects" adds a new quick link to navigate to the "Projects" list of the
+        corresponding secondary node.
+        On secondary nodes, a new "All" tab gives you a quick overview about the verification state
+        of all projects.
+
+        [Further UX improvements](https://gitlab.com/groups/gitlab-org/-/epics/369) are in our pipeline!
+
     - name: "Prometheus 2.0 upgrade for Omnibus GitLab"
       available_in: [core, starter, premium, ultimate]
       gitlab_com: false
@@ -588,35 +610,31 @@ features:
         These include improved performance and a more efficient time-series database format. Unfortunately
         because of the architectural changes to the database, it is not backwards compatible with the old 1.x format.
-        With GitLab 11.4, Prometheus 2.4.2 is now available in the Omnibus package so users can take advantage its benefits.
+        With GitLab 11.4, Prometheus 2.4.2 is now available in the Omnibus package so users can take advantage of its benefits.
         - New installations of 11.4 and above will start with Prometheus 2.
         - Existing installations will not be automatically upgraded. We have added a new command, `gitlab-ctl prometheus-upgrade`, which can
         be utilized to [upgrade Prometheus and optionally migrate data](https://docs.gitlab.com/omnibus/update/gitlab_11_changes.html#11-4). Prometheus will be stopped during data migration.
-        - Users will need to move to Prometheus 2.0, before being able to [upgrade to GitLab 12.0](#deprecations).
+        - GitLab 12.0 will [automatically upgrade to Prometheus 2.0](#deprecations). With the automatic upgrade, Prometheus 1.0 data will not be migrated.
         For more information on upgrading Prometheus to 2.4.2, please review our [update documentation](https://docs.gitlab.com/omnibus/update/gitlab_11_changes.html#11-4).
-    - name: "Geo UX improvements in Admin Area"
+    - name: "Geo improvements"
       available_in: [premium, ultimate]
       gitlab_com: false
       documentation_link: 'https://docs.gitlab.com/ee/administration/geo/replication/configuration.html'
-      image_url: '/images/11_4/geo_admin_area_improvements.png'
       reporter: akaemmerle
-      team: geo
-      issue_url: 'https://gitlab.com/gitlab-org/gitlab-ee/issues/7126'
+      issueboard_url: 'https://gitlab.com/groups/gitlab-org/-/boards/796982?scope=all&utf8=✓&state=opened&label_name[]=Geo&milestone_title=11.4'
       description: |
-        As a Geo admin, keeping an overview of your secondary nodes setup and the synchronization
-        state is crucial when working with distributed teams.
-        With GitLab 11.4, we improve the Geo-related Admin Area settings by improving and showing even
-        more synchronization and verification details in the user interface. On your primary node, a
-        new button "Open projects" adds a new quick link to navigate to the "Projects" list of the
-        corresponding secondary node.
-        On secondary nodes, a new "All" tab gives you a quick overview about the verification state
-        of all projects.
-        [Further UX improvements](https://gitlab.com/groups/gitlab-org/-/epics/369) are in our pipeline!
+        We continually focus on improving our [Geo](/features/gitlab-geo/) feature for distributed teams. Some of the additional noteworthy improvements in GitLab 11.4 include:
+        - [Major performance improvements](https://gitlab.com/groups/gitlab-org/-/issues?scope=all&utf8=✓&state=closed&label_name%5B%5D=Geo%20Performance&milestone_title=11.4)
+        - [Include keep-around references in checksum calculation](https://gitlab.com/gitlab-org/gitlab-ee/issues/5196)
+        - [Migrating uploads to object storage does no longer leave behind local files](https://gitlab.com/gitlab-org/gitlab-ee/issues/7108)
+        - [Primary node repository verification now always gives the correct checksum](https://gitlab.com/gitlab-org/gitlab-ee/issues/7213)
+        - [Reliable Sidekiq queueing ensures data integrity](https://gitlab.com/gitlab-org/gitlab-ee/issues/7279)
+        Read our fresh blog post on [how we built GitLab Geo](/2018/09/14/how-we-built-gitlab-geo/).
     - name: "Geo improvements for SSH Git commands proxy to primary node"
       available_in: [premium, ultimate]
@@ -633,23 +651,6 @@ features:
         With this release, we further improve the performance and usability of this feature, allowing
         to clone and push to projects in a Geo scenario without having to maintain multiple configurations or update the remote URL manually.
-    - name: "Geo improvements"
-      available_in: [premium, ultimate]
-      gitlab_com: false
-      documentation_link: 'https://docs.gitlab.com/ee/administration/geo/replication/configuration.html'
-      reporter: akaemmerle
-      issueboard_url: 'https://gitlab.com/groups/gitlab-org/-/boards/796982?scope=all&utf8=✓&state=opened&label_name[]=Geo&milestone_title=11.4'
-      description: |
-        We continually focus on improving our [Geo](/features/gitlab-geo/) feature for distributed teams. Some of the additional noteworthy improvements in GitLab 11.4 include:
-
-        - [Major performance improvements](https://gitlab.com/groups/gitlab-org/-/issues?scope=all&utf8=✓&state=closed&label_name%5B%5D=Geo%20Performance&milestone_title=11.4)
-        - [Include keep-around references in checksum calculation](https://gitlab.com/gitlab-org/gitlab-ee/issues/5196)
-        - [Migrating uploads to object storage does no longer leave behind local files](https://gitlab.com/gitlab-org/gitlab-ee/issues/7108)
-        - [Primary node repository verification now always gives the correct checksum](https://gitlab.com/gitlab-org/gitlab-ee/issues/7213)
-        - [Reliable Sidekiq queing ensures data integrity](https://gitlab.com/gitlab-org/gitlab-ee/issues/7279)
-
-        Read our fresh blog post on [how we built GitLab Geo](/2018/09/14/how-we-built-gitlab-geo/).
-
     - name: "GitLab Runner 11.4"
       available_in: [core, starter, premium, ultimate]
       documentation_link: 'https://docs.gitlab.com/runner'
@@ -680,7 +681,7 @@ features:
       reporter: joshlambert
       team: distribution
       description: |
-        - `redis` has been updated to 3.2.12, which is a critical security update that fixes multiple vulnerabilities. After upgrating to 11.4, run `gitlab-ctl restart redis` to ensure the new version is running.
+        - `redis` has been updated to 3.2.12, which is a critical security update that fixes multiple vulnerabilities. After upgrading to 11.4, run `gitlab-ctl restart redis` to ensure the new version is running.
         - GitLab 11.4 includes [Mattermost 5.3](https://mattermost.com/blog/mattermost-5-3-enhanced-search-on-desktop-and-mobile-plugin-hackathon-highlights-and-more/),
         an [open source Slack-alternative](https://mattermost.com/) whose newest release includes enhanced search on desktop and mobile, plus much more.
         It includes [security updates](https://about.mattermost.com/security-updates/) and upgrading is recommended.
@@ -710,7 +711,7 @@ mvp:
   fullname: "Luke Picciau"
   gitlab: Qwertie
   description: |
-    Luke added the ability to download 2FA codes as a file.
+    Luke added the ability to [download 2FA codes as a file](#download-two-factor-authentication-codes-as-file).
     
     Thank you, Luke for your contribution!
@@ -764,4 +765,5 @@ deprecations:
     description: |
       With GitLab 11.4 (October 22, 2018) the bundled Prometheus 1.0 version is deprecated in Omnibus GitLab. Prometheus 2.0 is [now included](#prometheus-20-upgrade-for-omnibus-gitlab),
       however the metrics format is incompatible with 1.0. Existing installations can upgrade to 2.0 and optionally migrate their data [using an included tool](https://docs.gitlab.com/omnibus/update/gitlab_11_changes.html#11-4).
-      Migration to 2.0 will be required in order to upgrade to GitLab 12.0.
+      
+      With GitLab 12.0 any installation not yet running Prometheus 2.0 will be automatically upgraded. Metric data from Prometheus 1.0 will not be migrated, and will be lost.