Release Train

In case you hadn’t noticed the world around us is moving really fastly — super charged by iPhones and “Apps” and personal clouds and public clouds and twitter and more all in the shadow of cyber warfare and security. Behind the scenes revolutions in the software industry are going on as the Google’s, and Microsoft’s, and Apple’s, and Amazon’s, and NetFlix’s of the world are taking on big established players like IBM, and Oracle, and Cisco and whoever else is out there.


Within this nuttiness software development teams are still building code, testing it, and releasing it. One of the biggest pains in the ass with developing code and then testing it, is testing the code in so many different environments. That’s where DevOps (development and operations) software and practices have taken on a footing.

At the top end, you need to manage Releases of software — many related applications potentially — thru a release cycle — with bugs fixed and enhancements made (or not), software compiled, tested, and released. New software programs focusing on this release train have come on the market. There is a vocabulary of terms used in Release management:

  • Initiative: Releases contain a collection of changes to your Application(s) code base to effect an Initiative – a larger effort towards a goal(s)
  • Code Changes: code changes to the software are kept in a source control database such as GIT.
  • Release: contains one or more applications scheduled for release.
  • Application(s): contains one or more components of software.
  • Pipeline: a view of multiple releases of software (applications related to one another) in a timeline thru gates.

Be the first to comment

Leave a Reply

Your email address will not be published.


This site uses Akismet to reduce spam. Learn how your comment data is processed.