GitLab 9.4 release post

Review Apps link: https://release-9-4.about.gitlab.com/2017/07/22/gitlab-9-4-released/

Items link: https://gitlab.com/gitlab-com/www-gitlab-com/blob/release-9-4/data/release_posts/2017_07_22_gitlab_9_4_released.yml
Intro link: https://gitlab.com/gitlab-com/www-gitlab-com/blob/release-9-4/source/posts/2017-07-22-gitlab-9-4-released.html.md

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: 07/16 (6th working day before the 22nd)

• Label MR: blog post release
• Add milestone
• Intro
• MVP
• Add cover image image_title (compressed)
• Upgrade barometer
• Top feature
• Performance improvements
• Omnibus improvements
• Deprecations
• Documentation links
• Add features to data/features.yml
• Authorship (author's data)

Features

PMs: please check your box only when all your features and deprecations were added with completion (documentation links, images, etc). Pls don't check your item if there are still things missing.

• Fabio - CI/CD
• Victor - Discussion
• Mark - I2P
• Mike - Platform
• Joshua- Monitoring
• Stan - Geo
• Job - Edge

Tip: make your own checklist:

• Primary features
• Improvements (secondary features)
• Deprecations
• Documentation links
• Illustrations
• Update features.yml

Review

Content review (PMs)

Due date: 07/20 (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 (tech writers, content marketing)
  • Title
  • Description
  • Grammar, spelling, clearness (body)
• Marketing review (Amara)
• Final review (Job)

Structural Check

Due date: 07/20 (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_07_22_gitlab_9_4_released.yml

@@ -82,7 +82,15 @@ features:
       description: | # supports markdown
         Lorem ipsum [dolor sit amet](#link), consectetur adipisicing elit.
         Perferendis nisi vitae quod ipsum saepe cumque quia `veritatis`.
-
+        
+    - name: Slack app for GitLab.com
+      available_in: [GitLab.com only] # required
+      documentation_link: 'https://docs.gitlab.com/#lorem' # webpage or documentation - optional
+      documentation_text: "Learn more about Lorem" # optional
+      image_url: '/images/9_X/feature-a.png' # required
+      description: | # supports markdown
+        We've already had support for Slack integration in GitLab in the past. With this release, we now have a GitLab.com app right in the Slack App Directory itself. This signficantly makes it easier to configure Slack integration, reducing many manual steps. We are supporting the integration for GitLab.com only in this release.
+        
 # SECONDARY FEATURES
   secondary:
     - name: Lorem ipsum
@@ -107,6 +115,34 @@ features:
         Lorem ipsum [dolor sit amet](#link), consectetur adipisicing elit.
         Perferendis nisi vitae quod ipsum saepe cumque quia `veritatis`.
+    - name: Simplified JIRA integration settings
+      available_in: [ce] 
+      documentation_link: 'https://docs.gitlab.com/#' # webpage or documentation - optional
+      documentation_text: "Praesentium tempore nulla asperiores" # optional
+      description: | # supports markdown
+        We've simplified the JIRA integration settings to make it even more easier to configure. You know longer have to specify a particular JIRA project as part of the configuration. Your GitLab project knows to communicate with any JIRA project in the specified JIRA instance.
+        
+    - name: Trello Power-Up to attach merge request
+      available_in: [ce] 
+      documentation_link: 'https://docs.gitlab.com/#' # webpage or documentation - optional
+      documentation_text: "Praesentium tempore nulla asperiores" # optional
+      description: | # supports markdown
+        You can now attach a GitLab merge request from within a Trello card. We've created a Trello Power-Up for this integration.
+
+    - name: Unified Slack interface
+      available_in: [ce] 
+      documentation_link: 'https://docs.gitlab.com/#' # webpage or documentation - optional
+      documentation_text: "Praesentium tempore nulla asperiores" # optional
+      description: | # supports markdown
+        With this release, we are unifying the issue information shown in Slack in response to a link being pasted, a Slack slash command being executed, or a Slack notification. This provides a coherent experience regardless of how an issue is referenced in Slack.
+        
+    - name: Re-designed group milestones
+      available_in: [ce] 
+      documentation_link: 'https://docs.gitlab.com/#' # webpage or documentation - optional
+      documentation_text: "Praesentium tempore nulla asperiores" # optional
+      description: | # supports markdown
+        GitLab group milestones have been totally re-designed in this release. Prior, creating and managing a group milestone meant handling multiple project milestones in that group. With this release, we have _native_ group milestones, in addition to existing project milestones. For any issue, you can assign it a project milestone (from its project), same as before. But you can now also assign it a group milestone (from the project's group). You can now more easily manage issues at the group level, pulling in all assigned issues for a given group milestone.
+
     - name: Omnibus Improvements
       available_in: [ce, ees, eep] # required
       documentation_link:  # webpage or documentation - optional