Movatterモバイル変換


[0]ホーム

URL:


Skip to content
DEV Community
Log in Create account

DEV Community

Mike
Mike

Posted on

     

Let’s talk release management

I’m often working on ways to improve my own releases, and wanted to crowdsource some information - how do you do your releases?

Here’s how I do it:

  1. There’s a repo on private gitlab server on how to release each product, along with deployment and staging guidelines, devops code in another repo

  2. When you take on releases, you write an informative changelog, broadcast the upcoming release

  3. Before the release goes live, there’s a devops freeze, preventing anyone from deploying to staging and production momentarily so we can test this RC

  4. Upon approval, a third party will do a once over, and finally merge the changelog in, once the changelog is merged, the release is tagged, and CI kicks off building

  5. Once we’ve built and distributed, we upgrade our production servers, this takes about 20 minutes in total

  6. Devops freeze lifted on staging and dev, cycle over

  7. Release manager documents what they did, how long it took, thoughts/ideas for next time, and commits this to the release management repo

Top comments(0)

Subscribe
pic
Create template

Templates let you quickly answer FAQs or store snippets for re-use.

Dismiss

Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment'spermalink.

For further actions, you may consider blocking this person and/orreporting abuse

Full-time freelancer; Former Lead Engineer / Senior Management; speaker; 14 years in development; open for consulting and freelance opportunities.
  • Location
    Canada
  • Work
    Founder / CEO
  • Joined

Trending onDEV CommunityHot

DEV Community

We're a place where coders share, stay up-to-date and grow their careers.

Log in Create account

[8]ページ先頭

©2009-2025 Movatter.jp