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

@@ -299,21 +299,6 @@ features:
         services, like Kubernetes, to access your images every time it's needed,
         without giving your full credentials or using a dummy user for this task.
-    - name: Performance Impact of Merge Requests now Quantified
-      available_in: [ce, ees, eep]
-      documentation_link: 'https://docs.gitlab.com/ce/user/project/integrations/prometheus.html#determining-the-performance-impact-of-a-merge'
-      documentation_text: "Learn more about our monitoring your apps with Prometheus"
-      image_url: '/images/9_3/metrics-quantified.png'
-      description: |
-        With
-        [GitLab 9.2](/2017/05/22/gitlab-9-2-released/#app-performance-feedback-on-merge-requests)
-        we added the ability to see the memory impact of a merge,
-        by adding a sparkline to the Merge Request page. As part of GitLab 9.3 we are taking this
-        further and now quantify the change in average memory usage for the 30 minutes before and after the merge. 
-        
-        It is now easier than ever for developers to be cognizant of the impact they are
-        having on service performance, by getting direct feedback within the tool they already use every day. 
-
     - name: Object Storage for CI Artifacts
       available_in: [eep]
       documentation_link: 'https://docs.gitlab.com/ee/administration/job_artifacts.html#using-object-storage'
@@ -352,6 +337,21 @@ features:
         to create and manage Pipeline Schedules through a set of API,
         in order to allow integration with other tools simple and effective.
+    - name: Performance Impact of Merge Requests now Quantified
+      available_in: [ce, ees, eep]
+      documentation_link: 'https://docs.gitlab.com/ce/user/project/integrations/prometheus.html#determining-the-performance-impact-of-a-merge'
+      documentation_text: "Learn more about our monitoring your apps with Prometheus"
+      image_url: '/images/9_3/metrics-quantified.png'
+      description: |
+        With
+        [GitLab 9.2](/2017/05/22/gitlab-9-2-released/#app-performance-feedback-on-merge-requests)
+        we added the ability to see the memory impact of a merge,
+        by adding a sparkline to the Merge Request page. As part of GitLab 9.3 we are taking this
+        further and now quantify the change in average memory usage for the 30 minutes before and after the merge. 
+        
+        It is now easier than ever for developers to be cognizant of the impact they are
+        having on service performance, by getting direct feedback within the tool they already use every day. 
+
     - name: Debian 9 Support
       available_in: [ce, ees, eep]
       description: |