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

@@ -62,16 +62,21 @@ features:
         With the first iteration of Multi-Project Pipelines, GitLab 9.3 displays links for upstream and downstream projects directly on the pipeline graph, so developers can check the overall status of the entire pipeline chain in one single view.
-    - name: Code Quality results in the merge request widget area
+    - name: GitLab Code Quality
       available_in: [ees, eep]
       documentation_link: 'https://docs.gitlab.com/ee/user/project/merge_requests/code_quality_diff.html'
-      documentation_text: "Learn more about exposing Code Quality results in your merge requests"
+      documentation_text: "Learn more about GitLab Code Quality"
       image_url: '/images/9_3/code_climate.png'
       description: |
-        When submitting new code to a CI pipeline, you can automatically have a quality report (based on Code Climate) that shows if there are possible improvements or known issues in your source code.
-
-        Going a step further, GitLab 9.3 can now show the Code Quality report right in the merge request widget area in a very effective way.
-        The summary could be expanded to access details with exact references to code, allowing you to see differences before merging the branch.
+        When submitting new code with a [GitLab CI/CD](/features/gitlab-ci-cd/) pipeline,
+        you can automatically have a quality report (based on
+        [Code Climate](https://codeclimate.com/)) that shows if there are possible
+        improvements or known issues in your source code.
+
+        Going a step further, GitLab 9.3 can now show the Code Quality report right
+        in the merge request widget area in a very effective way.
+        The summary could be expanded to access details with exact references to code,
+        allowing you to see differences before merging the branch.
     - name: Protected Variables for enhanced pipelines security
       available_in: [ce, ees, eep]