Visual Studio ALM Rangers Transparency – Clarifying the processes: Release (Part 3)

We continue from Visual Studio ALM Rangers Transparency – Clarifying the processes: Projects (Part 1) and Visual Studio ALM Rangers Transparency – Clarifying the processes: Guidance (Part 2), which covered the high level project and guidance project views. In this post we will have a closer look at release process that each project lead goes through when preparing for BETA, Release Candidate (RC) or Release To Market (RTM).

Remember that the objective is to create a consolidated and easy to follow map of common ALM Ranger tasks as part of projects, in this case a Guidance project.

To cut a long story short, let us look at the steps that each ALM Rangers project team goes through when it is time to “click” the launch button and watch the hard work, the long nights and the endless commitment and passion is presented for release.

1. Once the deliverables have gone through the numerous reviews, as discussed in previous posts, it is up to the product owner to approve the release to “ship”. In essence the project team goes into a deadlock until they get the following signal from the PO:
   … after which a wave of activity is triggered.
2. All documentation receives a watermark to clearly indicate the relevant release status, ranging from ALPHA, BETA, RC to no watermark, which indicates that the artefacts are part of a major release, i.e. v1, v2, etc.
3. Any source code that is included with tooling and guidance projects is validated to ensure that it adheres to the sample source guidelines and has gone through relevant code reviews and assessments. Binaries, such as tools, DLLs and installers have to go through additional assessments and approval checkpoints and are typically not included in ALPHA or BETA releases.
4. All the bits and pieces needed to publish the release on Codeplex are packaged in one ZIP file. The bits and pieces include:
   - Hands-on Lab (HOL) Package Zip
   - All documentation in PDF format
   - All videos in 1280x720 dimension format
   - Other supporting bits, such as capacity planning workbooks
   - Download release notes
5. The backlog is updated, whereby all completed and approved (point 1) Epics are switched to done and the remaining work, if any, is pruned for the next iteration.
6. The last step, before the project leads enjoys a cool beer, is to drop the release package in the appropriate drop point, which triggers the publication on Codeplex by the support team.
7. The team then continues with the next iteration, for example aiming for the release candidate, or switch to maintenance mode if they have just released the RTM.

Every ALM Rangers solution is geared at delivering value to the community and your candid feedback and success stories is an important catalyst and fuel for the next lifecycle of the project. :)

Comments

• Anonymous
  February 09, 2012
  Re. one Zip file, this is ok as the default download, but I would like to have the main guidance document (at least) available as a single download. Sometime I just need the 500k doc, not the 80Mb package. Mike

• Anonymous
  February 09, 2012
  Mike, great comment! This series of blog posts documents our internal processes and guidance, intended as a reference for the Rangers and as a trasparent insight to the community. The BETA Package mentioned is the package the project leads submit to the support team, who in turn unpackage when creating the download packages on Codeplex. We are not planning to change the default of including:

• The main guidance document as a seperate and the default download.
• One ZIP with all documents included
• One ZIP with the HOL Package
• Videos We are not sure whether to package all Videos in a ZIP and uploading them to Channel 9 as seperate videos, or adding the videos as seperate download items as well. Feedback from the community would be appreciated :)