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

@@ -417,34 +417,30 @@ deprecations:
   - feature_name: Subgroup support on MySQL
     due: June 22nd 2017
     description: |
-      This only supports one line!
-    # TODO:
-    # NB NB NB NB NB NB NB NB NB NB NB NB NB NB NB NB NB NB NB NB NB NB NB NB
-    # WE NEED A BETTER HOME FOR THIS, IT'S NOT A DEPRECATION!
-      # In 9.0 we released an enhancement to group management by
-      # [introducing subroups](https://about.gitlab.com/2017/03/22/gitlab-9-0-released/#subgroups-ce-ee).
-      # Unfortunately for performance and consistency, we have to drop this
-      # feature on GitLab instances running MySQL. Subgroups will no longer be
-      # available on MySQL in GitLab 9.3 and the upgrade process will migrate any
-      # subgroups to the root of the GitLab server.
-      #
-      # While investigating some occurrences of inconsistencies with project
-      # membership, we [discovered](https://gitlab.com/gitlab-org/gitlab-ce/issues/30472#note_27747600)
-      # that our approach to implementing subgroups was
-      # not efficient. While PostgreSQL provides easy workarounds, MySQL
-      # unfortunately did not provide any alternatives that did not require vastly
-      # changing the way we store the hierarchy of groups.
-      #
-      # In order to quickly address the issue, we have removed support from
-      # subgroups in 9.3.
-      #
-      # If you are running on MySQL and have created subgroups in your GitLab
-      # instance, the upgrade process will convert any subgroups to regular groups.
-      #
-      # We continue to support MySQL in general, although some features such as
-      # [GitLab Geo](https://docs.gitlab.com/ee/gitlab-geo/) and
-      # [Zero-downtime migrations](https://gitlab.com/gitlab-org/gitlab-ce/issues/26130)
-      # are only available on PostgreSQL.
+      In 9.0 we released an enhancement to group management by
+      [introducing subroups](https://about.gitlab.com/2017/03/22/gitlab-9-0-released/#subgroups-ce-ee).
+      Unfortunately for performance and consistency, we have to drop this
+      feature on GitLab instances running MySQL. Subgroups will no longer be
+      available on MySQL in GitLab 9.3 and the upgrade process will migrate any
+      subgroups to the root of the GitLab server.
+
+      While investigating some occurrences of inconsistencies with project
+      membership, we [discovered](https://gitlab.com/gitlab-org/gitlab-ce/issues/30472#note_27747600)
+      that our approach to implementing subgroups was
+      not efficient. While PostgreSQL provides easy workarounds, MySQL
+      unfortunately did not provide any alternatives that did not require vastly
+      changing the way we store the hierarchy of groups.
+
+      In order to quickly address the issue, we have removed support from
+      subgroups in 9.3.
+
+      If you are running on MySQL and have created subgroups in your GitLab
+      instance, the upgrade process will convert any subgroups to regular groups.
+
+      We continue to support MySQL in general, although some features such as
+      [GitLab Geo](https://docs.gitlab.com/ee/gitlab-geo/) and
+      [Zero-downtime migrations](https://gitlab.com/gitlab-org/gitlab-ce/issues/26130)
+      are only available on PostgreSQL.
   - feature_name: openSUSE 42.1 Support
     due: June 22nd, 2017.
     description: |