Skip to content

Release post - GitLab 10.3

Fabio Busatto requested to merge release-10-3 into master

Release post - GitLab 10.3 🚀

Review Apps link: https://release-10-3.about.gitlab.com/2017/12/22/gitlab-10-3-released/

Release post:

Related files:

Handbook references:

General Contributions

Due date: 2017-12-14 (6th working day before the 22nd)

All contributions added by team members, collaborators, and Product Managers (PMs).

Author's checklist

Due date: 2017-12-14 (6th working day before the 22nd)

The PM leading the post is responsible for adding and checking the following items:

  • Label MR: ~"blog post" release
  • Assign the MR to yourself
  • Add milestone
  • Update the links and due dates in this MR description
  • Make sure the blog post initial files, as well as this MR template contain the latest templates
  • Add authorship (author's data)
  • Add Introduction
  • Add MVP (feature block)
  • Add MVP to data/mvps.yml
  • Add cover image (image_title) (scaled and compressed)
  • Add social sharing image (twitter_image) (scaled and compressed)
  • Add Performance improvements
  • Make sure all feature descriptions are positive and cheerful
  • Make sure all the features listed in the direction page are included in the post
  • @mention the release manager to remind them to add the upgrade barometer section
  • Make sure Upgrade barometer is in
  • Check which one is the top feature (with Job and William)
  • Check if deprecations are included
  • Check if a webcast is being promoted
  • Check if new Mattermost is included (every other release)
  • Alert people one working day before each due date (post a comment to #release-post Slack channel)
  • Perform the content review
  • Remove remaining template sections
  • Assign the MR to the next reviewer

The following sections are always present, and managed by the PM owning the related product area:

  • Add GitLab Runner improvements: Fabio
  • Add Omnibus improvements: Joshua

Feature blocks

Due date: 2017-12-14 (6th working day before the 22nd)

The Product Managers are responsible for adding their feature blocks to the release post by the due date for general contributions.

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

  • Fabio
  • James
  • Joshua
  • Mark
  • Mike
  • Victor

Tip: make your own checklist:

  • Primary features
  • Improvements (secondary features)
  • Deprecations
  • Documentation updated
  • Documentation links added to the post
  • Illustrations added to the post (compressed)
  • Update features.yml (with accompanying screenshots)

Review

Ideally, complete the review until the 4th working day before the 22nd, so that the 3rd and the 2nd working day before the release could be left for fixes and small improvements.

Content review

Due date: 2017-12-20 (2nd working day before the 22nd)

Performed by the PM leading the post:

  • Label MR: ~"blog post" release review-in-progress
  • Check all comments in the thread (make sure no contribution was left behind)
  • Check Features' names
  • Check Features' availability (CE, EES, EEP, EEU badges)
  • Check Documentation links (all feature blocks contain documentation_link)
  • Make sure documentation_link links to feature webpages when available
  • Update data/promo.yml
  • Features were added to data/features.yml (with accompanying screenshots)
  • Check all images size < 300KB (compress them all with TinyPNG or similar tool)
  • Pull master, resolve any conflicts
  • Make sure all discussions in the thread are resolved

Further reviews

Due date: 2017-12-20 (2nd working day before the 22nd)

  • Copyedit (Rebecca, Axil, or Marcia)
    • Title
    • Description
    • Grammar, spelling, clearness (body)
    • Social sharing text (for Twitter, FB, and LinkedIn)
    • Homepage blurb
  • Marketing review (William)
  • Final review (Job)

Structural Check

Due date: 2017-12-20 (2nd working day before the 22nd)

Performed by technical writers (Axil or Marcia):

  • 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)
  • Meaningful links (SEO)
  • Badges consistency (applied to all headings)
  • Double check documentation updates
  • Check documentation links (point to /ee/, not to /ce/)
  • Remove any remaining instructions
  • Remove HTML comments
  • Run deadlink checker (https://www.deadlinkchecker.com/)
  • Pull master
  • Update release template with any changes (if necessary)

Merge it 🚀

The PM leading the post is responsible for merging the MR and following up with possible adjustments/fixes.

The post is to be merged on the 22nd as soon as GitLab.com is up and running on the new release version, and all packages are publicly available. Not before. The usual release time is 15:00 UTC but it varies according to the deployment. Coordinate the timing with the release managers. Ask them to keep you in the loop.

After merging, wait a few minutes to see if no one spot an error (usually posted in #general), then share on Twitter, Facebook, and LinkedIn, or make sure someone does.

Edited by Mark Pundsack

Merge request reports