Blog Post for Safe Deployments

Proposal

Following our documentation work in gitlab-org/gitlab#215469 (comment 350734279), we have a few new features around safe deployments that tell a really compelling story when combined together. A blog post would be a great way to inform users about these great capabilities

• Limit the pipeline job concurrency resource_group
• Disallows deployments for old versions
• Deploy Freeze

Checklist

• If you have a specific publish date in mind (please allow 3 weeks' lead time)
  • Include it in the issue title
  • Give the issue a due date of a minimum of 2 working days prior
  • If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior
• If time sensitive
  • Add ~"Blog: Priority" label and supplied rationale in description
  • Mention @rebecca to give her a heads up ASAP
• If wide-spread customer impacting or sensitive
  • Add sensitive label
  • Mention @nwoods to give her a heads up ASAP
• If the post is about one of GitLab's Technology Partners, including integration partners, mention @TinaS, apply the Partner Marketing label, and see the blog handbook for more on third-party posts
• Indicate if supporting an event or campaign
• Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)