Release to the Test environment
Tag numbers are in the form of aim__rc_vxx.xx, e.g. if the most recent tag is aim__rc_v27.00, the next is aim__rc_v27.01 by incrementing .01. Once it reaches xx.99, the next is yy.00 (where yy=xx+1). The number of digits after the decimal point is fixed at 2. Each number is an identification.
- Each of the numbers in the tags is indicative of a sequential count.
- This provides the release manager with both a unique identifier for the tag and an indicator of the order of the release but nothing about the development life cycle and nothing about the complexity of the release.
The current release in the Test environment is from the Test tag with the highest number. The associated commit ID and Jira ticket confers information of changes that can be seen from Tags link in Bitbucket.
Release to the Production environment
The Production tag is in the form of aim_vxx.xx by removing “__rc” from the Test tag aim__rc_vxx.xx. Note down the Production tag number (e.g. if the most recent tag is aim__rc_v27.00, the Production tag is aim_v27.00). In cases that do not have a Test tag, the next tag number is simply an increment of .01 in the numeric portion of the most recent Production tag.
The current release in the Production environment is from the Production tag with the highest number. The associated commit ID and Jira ticket confers more information of changes that can be seen from Tags link in Bitbucket.
Developers update their RM software (SourceTree) based on RMs’ recommendation.