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

@@ -364,13 +364,20 @@ features:
         These include x, y, z, and we will continue to add additional metrics
         in subsequent releases.
-    - name: Performance impact of merge request now quantified
+    - name: Performance Impact of Merge Request are now Quantified
       available_in: [ce, ees, eep]
       documentation_link: ''
       documentation_text: "Learn more "
       image_url:
       description: |
-        With GitLab 9.2, we added the ability to see the memory impact of a merge request, by adding a sparkline to the MR flow. As part of GitLab 9.3, we are taking this further and can now quantify the change in memory usage before and after the merge. It is now easier than ever for developers to be cognizant of the impact they are having on overall service performance, driving alignment across teams as delighting customers is everyone's job.
+        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 request,
+        by adding a sparkline to the MR flow. As part of GitLab 9.3, we are taking this
+        further and can now quantify the change in memory usage before and after the merge.
+        It is now easier than ever for developers to be cognizant of the impact they are
+        having on overall service performance, driving alignment across teams as
+        delighting customers is everyone's job.
     - name: Debian 9 support
       available_in: [ce, ees, eep]