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

@@ -78,17 +78,22 @@ features:
         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
+    - name: Protected Variables for Enhanced Pipelines Security
       available_in: [ce, ees, eep]
       documentation_link: 'https://docs.gitlab.com/ee/ci/variables/#protected-secret-variables'
-      documentation_text: "Learn more about protected secret variables"
+      documentation_text: "Learn more about Protected Secret Variables"
       image_url: '/images/9_3/protected_variables.png'
       description: |
-        Secret variables are very useful if you want to avoid external people to access private information for your project, but users that are able to modify the
-        project could still get access to it. This might cause unintended people to affect production envirments even if they've no permissions on the `master` branch.
-
-        In GitLab 9.3, Protected Variables introduce an additional layer of security to your sensitive information, such as deploy credentials.
-        Marking a variable as "protected" makes it available only to jobs running on protected branches, and so only authorized users can get access to it.
+        Secret variables are very useful if you want to avoid external people to
+        access private information for your project, but users that are able to modify the
+        project could still get access to it.
+        This might cause unintended people to affect production environments even if
+        they have no write permissions to the `master` branch.
+
+        In GitLab 9.3, **Protected Variables** introduce an **additional layer of security**
+        to your sensitive information, such as deploy credentials.
+        Marking a variable as "protected" makes it available only to jobs running on
+        protected branches, therefore only authorized users can get access to it.
     - name: Automated monitoring for system services
       available_in: [ce, ees, eep]