Fortified Bikesheds

Release Management in the Real World

Monday, October 22, 2012

Better AWS Status Reporting

Don't know where he gets his info, but he's sure on top of it:

https://twitter.com/ylastic
Posted by CG at 4:18 PM No comments:
Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Newer Posts Older Posts Home
Subscribe to: Posts (Atom)

What's This?

"Release Management looks like a bike shed to most, so they will go happily applying paint to it, not realizing there's a nuclear missile silo hidden underneath."

This is about Release Management principles and techniques, unrelated to specific tools or languages.

Even though some people may recognize techniques I used in the past, none of my postings are meant to indicate that any of the companies I work for actually do anything close to what I say here.

Labels

Basics (9) Branching (11) Build Tools (21) Housekeeping (7) Lore (20) Process (12)

Story So Far

The goal of the first batch of posts is to describe a software build and release process which assumes that builds are not necessarily reproducible and expensive to perform, and also assumes a large number of independent development teams all working on some grand piece of software.

Good release management starts at the source, so the first few postings deal about source code control and change management, and how to mine the change data correctly.

Once we can reliably build stuff, we need to manage the build products, the artifacts, so they can be reused, tested and released.

Blogroll

  • Eric Sink
    Native AOT libraries with TypeScript
    2 years ago
  • Jay Kreps
    Concurrency is not a language thing anymore
    10 years ago
  • mikeal
  • Ted Dziuba

About Me

My photo
CG
Software development veteran with over twenty years of experience developing and releasing both enterprise and software as a service products for highly distributed real time applications.
View my complete profile

Followers

Blog Archive

  • ►  2016 (1)
    • ►  May (1)
  • ►  2015 (2)
    • ►  June (1)
    • ►  January (1)
  • ►  2014 (2)
    • ►  November (1)
    • ►  October (1)
  • ►  2013 (16)
    • ►  September (3)
    • ►  August (1)
    • ►  July (2)
    • ►  June (1)
    • ►  May (3)
    • ►  April (4)
    • ►  March (1)
    • ►  February (1)
  • ▼  2012 (24)
    • ▼  October (1)
      • Better AWS Status Reporting
    • ►  September (1)
    • ►  June (1)
    • ►  May (2)
    • ►  April (1)
    • ►  March (4)
    • ►  February (7)
    • ►  January (7)
  • ►  2011 (16)
    • ►  December (16)
Simple theme. Powered by Blogger.