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

@@ -95,28 +95,29 @@ features:
         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: Centralized Audit Log & Extended user audit actions
+    - name: Centralized Audit Log & Extended User Audit Actions
       available_in: [eep]
       documentation_link: 'https://docs.gitlab.com/ee/administration/audit_events.html#audit-log-admin-only'
-      documentation_text: "Learn more about audit log"
+      documentation_text: "Learn more about Audit Log"
       image_url: '/images/9_3/audit_log.png'
       description: |
         Many companies have the need for audit and compliance across the
-        entire development cycle. In GitLab 9.3 there is now a centralized
-        Audit Log that includes all audit events from all Groups, Projects
-        and user actions.
-        Additionally in GitLab EEP, existing user audit events that were
-        previously limited to just authentication events are
+        entire development cycle. In GitLab 9.3 the system administrator has
+        access to an improved centralized Audit Log that includes all audit
+        events from all Groups, Projects, and user actions.
+        Additionally, in GitLab Entreprise Edition Premium (EEP), the
+        existing [user audit](https://docs.gitlab.com/ee/administration/auditor_users.html#auditor-users) events, that were
+        previously limited to just authentication events, have been
         expanded to include the following actions:
-         * Add a new email address
-         * Remove an email address
-         * Password change
-         * Forget password
-         * Failed to login
-         * Add SSH key
-         * Grant OAuth access
+         - Add a new email address
+         - Remove an email address
+         - Password change
+         - Forget password
+         - Failed to login
+         - Add SSH key
+         - Grant OAuth access
     - name: Settings made simple
       available_in: [ce, ees, eep]