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)

source/posts/2017-06-22-gitlab-9-3-released.html.md

+---
+release_number: "9.3"
+title: "GitLab 9.3 Released with This Feature and That Feature"
+author: Name Surname
+author_gitlab: GitLab.com-username
+author_twitter: Twitter-username
+image_title: '/images/9_3/9_3-cover-image.jpg'
+description: "GitLab 9.3 Released with Main-CE-Feature, Main-EE-Feature, Secondary-Feature, Secondary-Feature, and much more!"
+twitter_image: '/images/tweets/gitlab-9-3-released.png'
+categories: release
+# extra_css:
+#  - release-posts.css
+# extra_js:
+#  - release-posts.js
+---
+
+<!--
+- Add the content here. _Ad hoc_ free until the 6th working day before the 22nd. After that, we'll freeze the post.
+- Content review: will take place during the 5th and the 4th working day before the 22nd.
+- Styles will be applied in the 3rd to 1st working day before the 22nd. How to apply styles: check the [handbook](/handbook/marketing/blog/relese-post/).
+
+**Use the merge request template "Release-Post", and please set the calendar date for each stage.**
+
+----
+
+## Introduction
+
+- Enter the introduction here
+
+## MVP
+
+- Name and Surname:
+- GitLab.com handle: https://gitlab.com/username
+- Contributed to:
+- Merge request link:
+- Short description (example below):
+
+"Jacopo made it possible to [undo marking a todo item as done in the todos list](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/8691). This is a huge productivity enhancement that helps you recover from mistakes in managing todos. Thanks Jacopo!"
+
+## Webcast
+
+- Date:
+- Link:
+- CTA text:
+
+## Cover image:
+
+```md
+<section class="release-post-section">
+[Cover image](https://www.pexels.com/photo/banaue-rice-terraces-164196/) licensed under [CC0](https://www.pexels.com/photo-license/).
+{:.note .text-center}
+</section>
+``
+
+## Upgrade Barometer
+
+- DESCRIBE HOW INVOLVED THE MIGRATIONS ARE. CAN USERS EXPECT MUCH DOWNTIME?
+- CHECK IF THERE ARE ANY MIGRATIONS THAT REMOVE OR CHANGE COLUMNS.
+- IF THERE ARE ONLY ADDITIONS OR NO MIGRATIONS CONFIRM THAT DEPLOY CAN BE WITHOUT DOWNTIME
+
+## Performance improvements
+
+Describe it as a feature.
+
+## Omnibus improvements
+
+- Describe all improvements here. Link to docs, issues, and MRs whenever applicable.
+
+## Extras
+
+Are there any extra stuff to be added, or noted? Please describe them here. E.g.: events, news, notifications, etc.
+
+## Deprecations
+
+Anything being deprecated? Please fill the following block. Copy and paste the items as much as necessary. Separate them with dashes.
+
+----
+
+- Feature name:
+- Available in: (CE/EES/EEP)
+- Due date:
+- Description:
+- Link to issue or MR:
+
+----
+
+-->
+
+<!-- FEATURES -->
+
+<!--
+
+## FEATURES
+
+For each feature added to the post, provide the required info. Use dashes to separate them. Push all related images to the MR and provide the correct link. Compress every image with [Tiny PNG](https://tinypng.com/) or similar tool.
+
+----
+
+- Feature name:
+- Available in: (CE/EES/EEP)
+- Feature weight: main, secondary, other
+- Documentation link:
+- Feature description, related images, and videos:
+
+----
+
+Example:
+
+- Feature name: Deploy Boards
+- Available in: EEP
+- Feature weight: main
+- Documentation link: https://docs.gitlab.com/ee/user/project/deploy_boards.html
+- Feature description, related images, and videos:
+
+Today with 9.0, we are excited to release Deploy Boards for environments running on Kubernetes. The Environments page of Pipelines now offers a single place to view the current health and deployment status of each environment, displaying the specific status of each pod in the deployment. Developers and other teammates can view the progress and status of a rollout, pod by pod, in the workflow they already use without any need to access Kubernetes.
+
+![Deploy Boards](/images/9_0/deploy_boards.png){: .shadow}
+
+Watch the video:
+
+<figure class="video_container">
+  <iframe src="https://www.youtube.com/embed/enMumwvLAug" frameborder="0" allowfullscreen="true"> </iframe>
+</figure>
+
+----
\ No newline at end of file