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

@@ -294,7 +294,22 @@ features:
         `LICENSE` files are also analyzed, and the information about the specific
         license is easily accessible with a link for further details about it.
         Dependency management systems are also exposed to make it clear what the projects rely on.
-
+        
+    - name: System Note with Link to Change in Outdated Diff Discussion
+      available_in: [ce, ees, eep]
+      image_url: '/images/9_3/outdated_diff_discussion.png'
+      description: |
+        During merge request code review, we are constantly making code changes
+        and commenting on those changes. It is often difficult to keep track. In
+        particular, suppose we start commenting on a particular code line, and there
+        are subsequent changes to that line. You may end up discussing something
+        that has already changed. 
+        
+        With this release, we added a system note to indicate that a line has already 
+        changed, so that when you are participating in comments with respect to a 
+        particular line, you know that it's already been changed, and can even see 
+        the change by clicking through.
+        
     - name: Autolinking Package Names
       available_in: [ce, ees, eep]
       image_url: '/images/9_3/autolink.png'