GitLab 9.3 release post

Review Apps link: https://release-9-3.about.gitlab.com/2017/06/22/gitlab-9-3-released/

Release Post

• Blog handbook: https://about.gitlab.com/handbook/marketing/blog/
• Release post handbook: https://about.gitlab.com/handbook/marketing/blog/release-posts/

General Contributions

General contributions from the team.

Due date: 06/14 (6th working day before the 22nd)

• Label MR: blog post release
• Add milestone
• Intro
• MVP
• Add cover image image_title (compressed)
• Upgrade barometer
• Top features
• Primary features
• Secondary features (improvements)
• Performance improvements
• Omnibus improvements
• Deprecations
• Documentation links
• Authorship (author's data)

Review

Content review (PMs)

Due date: 06/19 (2nd working day before the 22nd)

• Label MR: blog post release review-in-progress
• General review (PM)
  • Check Features' names
  • Check Features' availability (CE, EES, EEP)
  • Check Documentation links
  • Update data/promo.yml
  • Check all images' size - compress whenever > 300KB
  • Meaningful links (SEO)
  • Check links to product/feature webpages
• Copyedit (Sean P, Rebecca, or Marcia)
  • Title
  • Description
  • Grammar, spelling, clearness (body)
• Final review (Job)

Structural Check

Due date: 06/19 (2nd working day before the 22nd)

• Label MR: blog post release review-structure
• Check frontmatter (entries, syntax)
• Check image_title and twitter_image
• Check image shadow {:.shadow}
• Check images' ALT text
• Videos/iframes wrapped in <figure> tags (responsiveness)
• Add/check <!-- more --> separator
• Add/check cover img reference (at the end of the post)
• Columns (content balance between the columns)
• Badges consistency (applied to all headings)
• Remove any remaining instructions
• Remove HTML comments
• Run deadlink checker
• Update release template with any changes (if necessary)

data/release_posts/2017_06_22_gitlab_9_3_released.yml

@@ -87,12 +87,12 @@ features:
         on Kubernetes by tracking CPU and Memory utilization. This was a great
         first step, and with GitLab 9.3 we are excited to launch significantly
         expanded support for other metrics and deployment types.
-        </p>
+
         Now with 9.3, GitLab will automatically detect [common system services](https://prometheus.io/docs/instrumenting/exporters/)
         like web servers and databases, tracking key metrics like throughput
         and load. With support for such a wider set of metrics, performance
         monitoring is now available for all deployments.
-        </p>
+
         <https://gitlab.com/gitlab-org/gitlab-ce/issues/28717>
         <https://gitlab.com/gitlab-org/gitlab-ce/issues/30369>
@@ -110,6 +110,7 @@ features:
         Additionally in GitLab EE, existing user audit events - that were
         previously limited to just authentication events in GitLab CI - are
         expanded to include the following actions:
+
          * Add a new email address
          * Remove an email address
          * Password change
@@ -130,11 +131,11 @@ features:
         Over time, the number of settings in GitLab has expanded as we've
         extended functionality and configuration options for projects and
         groups.
-        </p>
+
         In GitLab 9.3 we will [start to simplify the settings pages](https://gitlab.com/gitlab-org/gitlab-ce/issues/28451)
         by making the [Repository Settings](https://gitlab.com/gitlab-org/gitlab-ce/issues/30378)
         page a lot more readable.
-        </p>
+
         Settings will be better grouped and allow people to see an overview of
         all the settings available for a certain section.
@@ -161,13 +162,13 @@ features:
         GitLab in every release. Not only will this make individual instances
         of GitLab even faster, but will also greatly improve the performance
         of GitLab.com, an instance that has over 1 million users!
-        </p>
+
         In GitLab 9.3 we are continuing to make listing projects a lot faster
         and improving performance overall server performance by making changes
         to how we mirror repositories. Syntax highlighting on files will also
         be cached to improve overall performance and make viewing commits
         noticeably faster.
-        </p>
+
         There are [numerous other performance enhancements](https://gitlab.com/groups/gitlab-org/issues?scope=all&state=opened&utf8=%E2%9C%93&milestone_title=9.3&label_name%5B%5D=performance)
         in GitLab 9.3 that should not only make GitLab feel faster, but reduce
         overall impact on server infrastructure.
@@ -365,26 +366,29 @@ cta:
 # UPGRADE BAROMETER
 barometer:
   description: |
-    <p>To upgrade to GitLab 9.3, no downtime is required.</p>
-    <p>However we're also migrating data for CI jobs. If you have a significant number of jobs, this could take some time.
-    <p>Starting with GitLab 9.1.0 it's possible to upgrade to a newer version of GitLab
+    To upgrade to GitLab 9.3, no downtime is required.
+
+    However we're also migrating data for CI jobs. If you have a significant number of jobs, this could take some time.
+
+    Starting with GitLab 9.1.0 it's possible to upgrade to a newer version of GitLab
     without having to take your GitLab instance offline. However, for this to work
-    there are the following requirements:</p>
-    <ol>
-      <li>You can only upgrade 1 release at a time. For example, if 9.1.15 is the last
-      release of 9.1 then you can safely upgrade from that version to 9.2.0.
-      However, if you are running 9.1.14 you first need to upgrade to 9.1.15.</li>
-      <li>You have to use <a href="https://docs.gitlab.com/ce/development/post_deployment_migrations.html">post-deployment migrations</a>.</li>
-      <li>You are using PostgreSQL. If you are using MySQL you will still need downtime
-      when upgrading.</li>
-    </ol>
-    <p>This applies to major, minor, and patch releases unless stated otherwise in a
-    release post.</p>
-    <p>A new version of our API was released in <a href="https://about.gitlab.com/2017/03/22/gitlab-9-0-released/#api-v4">GitLab 9.0</a>.
+    there are the following requirements:
+
+      1. You can only upgrade 1 release at a time. For example, if 9.1.15 is the last
+         release of 9.1 then you can safely upgrade from that version to 9.2.0.
+         However, if you are running 9.1.14 you first need to upgrade to 9.1.15.
+      1. You have to use [post-deployment migrations](https://docs.gitlab.com/ce/development/post_deployment_migrations.html).
+      1. You are using PostgreSQL. If you are using MySQL you will still need downtime
+         when upgrading.
+
+    This applies to major, minor, and patch releases unless stated otherwise in a
+    release post.
+
+    A new version of our API was released in [GitLab 9.0](https://about.gitlab.com/2017/03/22/gitlab-9-0-released/#api-v4).
     While existing calls to API v3 will continue to work until August 2017, we
     advise you to make any necessary changes to applications that use the v3 API.
-    <a href="https://docs.gitlab.com/ee/api/v3_to_v4.html">Read the documentation</a> to learn
-    more.</p>
+    [Read the documentation](https://docs.gitlab.com/ee/api/v3_to_v4.html) to learn
+    more.
 # DEPRECATIONS
 deprecations: