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

@@ -7,7 +7,7 @@ features:
       image_url: '/images/11_4/batch-comments.png'
       reporter: victorwu
       team: plan
-      issue_url: https://gitlab.com/gitlab-org/gitlab-ee/issues/1984
+      issue_url: 'https://gitlab.com/gitlab-org/gitlab-ee/issues/1984'
       description: |
         Code review in merge requests is a powerful feature in GitLab. Team members
         have conversations linked to specific lines of code in a diff, and can even
@@ -17,8 +17,8 @@ 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 
-        allow a reviewer to draft as many code comments in a merge requests as they 
+        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
         even spread their work over many sessions, say starting a review on their
@@ -27,10 +27,12 @@ features:
         they appear as normal individual comments. This allows individual team members
         the flexibility to do code review however they want, but still being compatible
         with the entire team.
-        
-        In future iterations, we will improve the feature to provide a [preview](https://gitlab.com/gitlab-org/gitlab-ee/issues/4327)
+
+        In future iterations, we will improve the feature to provide a
+        [preview](https://gitlab.com/gitlab-org/gitlab-ee/issues/4327)
         before the batch submit action, and also combine all those notifications
-        that those comments currently generate, into [one batched notification](https://gitlab.com/gitlab-org/gitlab-ee/issues/4326).
+        that those comments currently generate, into
+        [one batched notification](https://gitlab.com/gitlab-org/gitlab-ee/issues/4326).
 # PRIMARY FEATURES
   primary:
@@ -70,7 +72,7 @@ features:
         Support for defining code owners was introduced in
         [GitLab 11.3](/2018/09/22/gitlab-11-3-released/#code-owners). In
-        upcoming releases, Code Owners will be further integrated into the
+        upcoming releases, code owners will be further integrated into the
         merge request workflow with
         [automatic assignment](https://gitlab.com/gitlab-org/gitlab-ee/issues/1012)
         and
@@ -86,33 +88,34 @@ features:
       issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/49801'
       description: | # supports markdown
         Now matter how engaged you are on GitLab, your activity is a relevant
-        source of information and engagement indicator, displayed right at your 
-        personal profile page. Showing your personal profile should immediately 
-        indicate what you are working on.
+        source of information and engagement indicator, displayed right at your
+        personal profile page. Your personal profile should give a simple insight
+        into what you are interested in and working on.
         With this release, we introduce a redesigned profile page overview, showing
-        your activity via a known, but shortened contribution graph with your latest
-        activities and your most relevant personal GitLab projects.
+        your activity via the familiar but shortened contribution graph with your
+        latest activities and your most relevant personal GitLab projects.
     - name: "Set and show your status message within the user menu"
       available_in: [core, starter, premium, ultimate]
       documentation_link: 'https://docs.gitlab.com/ee/user/profile/#current-status'
       image_url: '/images/11_4/user-menu-status.png'
+      image_noshadow: true
       reporter: akaemmerle
       team: manage
       issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/49075'
-      description: | 
-        With [GitLab 11.2](https://about.gitlab.com/2018/08/22/gitlab-11-2-released/#personal-status-messages/) 
-        we introduced personal status messages for the first time, allowing to 
+      description: |
+        With [GitLab 11.2](/2018/08/22/gitlab-11-2-released/#personal-status-messages)
+        we introduced personal status messages for the first time, allowing to
         share your current availability, mood or simply your favorite animal.
-        With this release, we make setting your status even more simple and frictionless.
-        A new "Set status" item in your user menu provides a fresh modal that allows
-        you to set and clear your status right within context.  
-        In addition, your set status is also shown in your user menu, on top of 
+        With this release, we make setting your status even more simple and
+        frictionless. A new "Set status" item in your user menu provides a fresh
+        modal that allows you to set and clear your status right within context.
+        In addition, your set status is also shown in your user menu, on top of
         your full name and user name, including set Emoji and message.
-    - name: "Move ability to use includes in `.gitlab-ci.yml` from Starter to Core"
+    - name: "Move ability to use includes in .gitlab-ci.yml from Starter to Core"
       available_in: [core, starter, premium, ultimate] # required
       documentation_link: 'https://docs.gitlab.com/ee/ci/yaml/#include' # required
       reporter: jlenny # required
@@ -128,7 +131,7 @@ features:
     - name: "Run jobs only/except when there are modifications on a given path or file"
       available_in: [core, starter, premium, ultimate] # required
-      documentation_link: 'https://docs.gitlab.com/ee/ci/yaml/#changes' # required
+      documentation_link: 'https://docs.gitlab.com/ee/ci/yaml/#only-changes' # required
       reporter: jlenny # required
       team: verify # required
       issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/19232' # required
@@ -144,7 +147,7 @@ features:
     - name: "Add feature flags for applications (ALPHA) **[PREMIUM]**"
       available_in: [premium, ultimate] # required
       documentation_link: 'https://docs.gitlab.com/ee/user/project/operations/feature_flags.html' # required
-      image_url: '/images/11_4/feature-flags.png' # required
+      image_url: '/images/11_4/feature_flags.png' # required
       reporter: jlenny # required
       team: release # required
       issue_url: 'https://gitlab.com/gitlab-org/gitlab-ee/issues/6220' # required
@@ -163,7 +166,7 @@ features:
     - name: "Add timed incremental rollouts to AutoDevOps **[PREMIUM]**"
       available_in: [premium, ultimate] # required
       documentation_link: 'https://docs.gitlab.com/ee/topics/autodevops/#timed-incremental-rollout-to-production' # required
-      image_url: '/images/11_4/timed-incremental-rollouts.png' # required
+      image_url: '/images/11_4/timed_incremental_rollouts.png' # required
       reporter: jlenny # required
       team: release # required
       issue_url: 'https://gitlab.com/gitlab-org/gitlab-ee/issues/7545' # required
@@ -287,7 +290,7 @@ features:
         Thank you [Jan Beckmann](https://gitlab.com/kingjan1999) for the URL link contribution!
-    - name: "Highlight `@mentions` for yourself distinctly"
+    - name: "Highlight @mentions 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'
@@ -369,20 +372,21 @@ features:
         You can close (and re-open) an epic via buttons on the epic, via quick actions
         in an epic comment, and also via the API, exactly like issues.
-    - name: "Improve Admin Area Settings structure"
+    - name: "Improve admin area settings structure"
       available_in: [core, starter, premium, ultimate]
       gitlab_com: false
       documentation_link: 'https://docs.gitlab.com/ee/user/admin_area/settings/'
       image_url: '/images/11_4/admin-area-settings.png'
+      image_noshadow: true
       reporter: akaemmerle
       team: manage
       issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/44998'
-      description: | 
-        Depending on your responsibilities, administrating GitLab can provide 
+      description: |
+        Depending on your responsibilities, administrating GitLab can provide
         a very complex challenge due to all things GitLab offers.
         With this release, we improve the experience of our Admin Area Settings by
-        moving all sections into new, individual Settings sub-pages. This provides 
+        moving all sections into new, individual Settings sub-pages. This provides
         Admins a time-saving shortcut to access any detail to manage.
     - name: "Explore project by most stars"
@@ -393,10 +397,10 @@ features:
       team: manage
       issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/47203'
       description: |
-        At GitLab, we try our best to enable you to provide any chance to explore
-        relevant and cool projects on your GitLab instance.  
-        With this release, a new filter "Most stars" provides an incredible useful 
-        filter to show projects most liked on your instance.
+        At GitLab, we do our best to enable you to explore relevant and cool projects
+        on your GitLab instance.
+        With this release, a new filter "Most stars" provides an incredible useful
+        filter to show projects most starred on your instance.
         Thank you for this contribution, [Jacopo Beschi](https://gitlab.com/jacopo-beschi)!
@@ -407,15 +411,15 @@ features:
       reporter: akaemmerle
       team: manage
       issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/51457'
-      description: | 
+      description: |
         We recently introduced a new code language bar on the Project overview page,
         providing a quick overview about programming languages involved.
-        With GitLab 11.4, we introduce a more absolute measure by showing a new 
-        percentage value for each relevant code language shown. This provides a 
+        With GitLab 11.4, we introduce a more absolute measure by showing a new
+        percentage value for each relevant code language shown. This provides a
         more quantative touch point of your project technology stack.
-        
-        Thank you for this contribution, [Johann Hubert Sonntagbauer](https://gitlab.com/johann.sonntagbauer)
+
+        Thank you for this contribution, [Johann Hubert Sonntagbauer](https://gitlab.com/johann.sonntagbauer)!
     - name: "Download two-factor authentication codes as file"
       available_in: [core, starter, premium, ultimate]
@@ -427,15 +431,15 @@ features:
       description: |
         Two-factor authentification is a de facto standard for signing up for any relevant web-based
         application. At GitLab we understand and take this serious. 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. 
+        authentication initially, we provide limited recovery codes that allow you to regain access
+        to your account as a fallback.
         With this release, we now support to download recovery codes via a new "Download codes" button
         in addition.
-        Thank you for this contribution, [Johann Hubert Sonntagbauer](https://gitlab.com/johann.sonntagbauer)
-    - name: "Filter Admin Runners view by Runner Type and State"
+        Thank you for this contribution, [Johann Hubert Sonntagbauer](https://gitlab.com/johann.sonntagbauer)!
+    - name: "Filter admin Runners view by Runner type and state"
       available_in: [core, starter, premium, ultimate] # required
       gitlab_com: false
       documentation_link: 'https://docs.gitlab.com/ee/ci/runners/' # required
@@ -476,7 +480,7 @@ features:
         example, when implementing timed incremental rollouts, or any
         other delays needed after performing some other action.
-    - name: "Skip auto devops jobs based on license"
+    - name: "Skip Auto DevOps jobs based on license"
       available_in: [core, starter, premium, ultimate] # required
       documentation_link: 'https://docs.gitlab.com/ee/topics/autodevops/' # webpage or documentation - required
       reporter: danielgruesso
@@ -490,9 +494,24 @@ features:
         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] # required
+      documentation_link: 'https://docs.gitlab.com/ee/user/project/clusters/#installing-applications/'
+      image_url: '/images/11_4/nurtch.png'
+      reporter: danielgruesso
+      team: configure
+      issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/45912'
+      description: | # supports markdown
+        Interactive runbooks provide a powerful way for operators to interact with various systems to carry out 
+        common tasks such as diagnosing, deploying, and measuring infrastructure components. 
+        
+        The JupyterHub app offered via GitLab's Kubernetes integration now ships with Nurtch's 
+        [Rubix library](https://github.com/amit1rrr/rubix), providing a simple way to create devops 
+        runbooks. A sample runbook is provided, showcasing common operations.
+    
     - name: "Add manual entries for License Management"
       available_in: [ultimate] # required
-      documentation_link: '' # https://gitlab.com/gitlab-org/gitlab-ee/issues/7971
+      documentation_link: 'https://docs.gitlab.com/ee/user/project/merge_requests/license_management.html#manual-license-management'
       image_url: '/images/11_4/license_management.png'
       reporter: bikebilly
       team: secure
@@ -529,7 +548,7 @@ features:
         Developers fetch refs many times a day to check if the current branch
         is behind the remote branch. Git protocol v2 is a major update to Git's
         [wire protocol](https://www.kernel.org/pub/software/scm/git/docs/technical/pack-protocol.html)
-        which defines how clones, fetches and pushes are communicated between
+        which defines how clones, fetches, and pushes are communicated between
         the client (your computer) and the server (GitLab). The new wire
         protocol improves the performance of fetch commands and enables future
         protocol improvements.
@@ -553,20 +572,55 @@ features:
       issue_url: 'https://gitlab.com/gitlab-org/omnibus-gitlab/issues/2940'
       description: |
         Omnibus GitLab comes out of the box with Prometheus, allowing [easy observability of deployed instances](https://docs.gitlab.com/ee/administration/monitoring/prometheus/).
-        The Prometheus team has released a major new version, the 2.x series,  which offers a 
+        The Prometheus team has released a major new version, the 2.x series, which offers a
         [number of improvements](https://prometheus.io/blog/2017/11/08/announcing-prometheus-2-0/).
         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.
-        * 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 
+        - 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).
+        - Users will need to move to Prometheus 2.0, before being able to [upgrade to GitLab 12.0](#deprecations).
         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"
+      available_in: [premium, ultimate]
+      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 are in our pipeline!
+
+    - name: "Geo improvements for SSH git commands proxy to primary node"
+      available_in: [premium, ultimate]
+      documentation_link: 'https://docs.gitlab.com/ee/administration/geo/replication/configuration.html'
+      image_url: '/images/11_4/geo_ssh_proxy_improvements.png'
+      reporter: akaemmerle
+      team: geo
+      issue_url: 'https://gitlab.com/gitlab-org/gitlab-ee/issues/7541'
+      description: |
+        Making Geo as easy to use as possible is one of our constant goals to support widely distributed 
+        teams using GitLab. In [11.3](https://about.gitlab.com/2018/09/22/gitlab-11-3-released/#geo-improvements)
+        we added initial support for proxying SSH `git push` from secondary to primary nodes.
+
+        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 update the remote URL manually.
+
     - name: "Geo improvements"
       available_in: [premium, ultimate]
       gitlab_com: false
@@ -574,13 +628,17 @@ features:
       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 noteworthy improvements in GitLab 11.4 include:
-        - xx
-        Read a fresh post [how we built GitLab Geo](/2018/09/14/how-we-built-gitlab-geo/).
-    - name: GitLab Runner 11.4
+        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'
       documentation_text: "Read through the documentation of GitLab Runner"
@@ -590,14 +648,14 @@ features:
         ##### Most interesting changes:
-        * [Support JSON logging](https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/1020)
-        * [Add docker support for interactive web terminal](https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/1008)
-        * [Add support docker machine web terminal support](https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/1046)
-        * [Allow disabling docker entrypoint overwrite](https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/965)
-        * [Add metrics with concurrent and limit values](https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/1019)
-        * [Add a gitlab_runner_jobs_total metric](https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/1018)
-        * [Add a job duration histogram metric](https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/1025)
-        * [Fix command and args assignment when creating containers with K8S executor](https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/1010)
+        - [Support JSON logging](https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/1020)
+        - [Add docker support for interactive web terminal](https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/1008)
+        - [Add support docker machine web terminal support](https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/1046)
+        - [Allow disabling docker entrypoint overwrite](https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/965)
+        - [Add metrics with concurrent and limit values](https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/1019)
+        - [Add a gitlab_runner_jobs_total metric](https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/1018)
+        - [Add a job duration histogram metric](https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/1025)
+        - [Fix command and args assignment when creating containers with K8S executor](https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/1010)
         List of all changes can be found in GitLab Runner's [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-runner/blob/v11.4.0/CHANGELOG.md).
@@ -620,17 +678,21 @@ features:
     - name: "Performance improvements"
       available_in: [core, starter, premium, ultimate]
-      performance_url: https://gitlab.com/groups/gitlab-org/merge_requests?scope=all&utf8=%E2%9C%93&state=merged&label_name%5B%5D=performance&milestone_title=11.4 # Link to the merged MRs in the corresponding milestone
+      performance_url: 'https://gitlab.com/groups/gitlab-org/merge_requests?scope=all&utf8=%E2%9C%93&state=merged&label_name%5B%5D=performance&milestone_title=11.4' # Link to the merged MRs in the corresponding milestone
       reporter: pm1 # required
       team: teamname # required
       description: | # supports markdown
         Some of the more noteworthy performance improvements in GitLab 11.4 include:
-        * [Rendering Markdown with many label references is faster](https://gitlab.com/gitlab-org/gitlab-ce/issues/48221)
-        * [Issue discussions with many cross-project commit references are faster](https://gitlab.com/gitlab-org/gitlab-ce/issues/43094)
-        * [Fetching related branches for an issue runs fewer queries](https://gitlab.com/gitlab-org/gitlab-ce/issues/43097)
-        * [Fetching environments for a merge request runs fewer queries](https://gitlab.com/gitlab-org/gitlab-ce/issues/43109)
-        * [Computing recipients for notification emails runs fewer queries](https://gitlab.com/gitlab-org/gitlab-ce/issues/47496)
+        - [Rendering Markdown with many label references is faster](https://gitlab.com/gitlab-org/gitlab-ce/issues/48221)
+        - [Issue discussions with many cross-project commit references are faster](https://gitlab.com/gitlab-org/gitlab-ce/issues/43094)
+        - [Fetching related branches for an issue runs fewer queries](https://gitlab.com/gitlab-org/gitlab-ce/issues/43097)
+        - [Fetching environments for a merge request runs fewer queries](https://gitlab.com/gitlab-org/gitlab-ce/issues/43109)
+        - [Computing recipients for notification emails runs fewer queries](https://gitlab.com/gitlab-org/gitlab-ce/issues/47496)
+        - [Creating a new diff discussion on a merge request is faster](https://gitlab.com/gitlab-org/gitlab-ce/issues/49002)
+        - [Fetching "Last commit" info in tree view makes fewer Gitaly calls](https://gitlab.com/gitlab-org/gitlab-ce/issues/37433)
+        - [Loading merge request is faster after removing dead code](https://gitlab.com/gitlab-org/gitlab-ce/issues/51172)
+
 # EXTRAS (Optional)
 # extras:
@@ -668,17 +730,22 @@ cta:
 barometer:
   reporter: pm1 # required
   description: | # example (supports markdown)
-    To upgrade to GitLab 11.4 from the latest 11.3 version, no downtime is required. To upgrade without downtime, please consult the [documentation on downtimeless upgrades](https://docs.gitlab.com/ee/update/README.html#upgrading-without-downtime).
-    For this release we have migrations, post-deploy migrations, and to help with the larger migrations we have introduced background migrations.
-    GitLab.com migrations took approximately 34 minutes and post-deploy migrations amounted for a total of around two minutes. Background migrations on the other hand are sidekiq jobs that will run synchronously, for this release these migrations took around Z days to complete, no side effects were expected nor present, these target older pipeline builds so newer executed pipelines are not affected.
+    To upgrade to GitLab 11.4 from the latest 11.3 version, no downtime is required. To upgrade
+    without downtime, please consult the [documentation on downtimeless upgrades](https://docs.gitlab.com/ee/update/README.html#upgrading-without-downtime).
+    For this release we have migrations, post-deploy migrations, and to help with the larger
+    migrations we have introduced background migrations.
+    GitLab.com migrations took approximately 34 minutes and post-deploy migrations amounted for a
+    total of around two minutes. Background migrations on the other hand are sidekiq jobs that will
+    run synchronously, for this release these migrations took around Z days to complete, no side
+    effects were expected nor present, these target older pipeline builds so newer executed pipelines are not affected.
     GitLab Geo users, please consult the documentation on [upgrading Geo](https://docs.gitlab.com/ee/administration/geo/replication/updating_the_geo_nodes.html).
 # DEPRECATIONS
 deprecations:
-  - feature_name: "Support for Docker Versions in GitLab Runner"
+  - feature_name: "Support for Docker versions in GitLab Runner"
     due: October 22, 2018
     reporter: jlenny
     description: |