Versioning & Release Process
SAIT uses version numbers to track features and bug fixes in our web applications; some of our web applications include a version number in the page footer. Each digit has a specific meaning...example version number: 1.2.3
1 = major release
(dramatic changes to functionality or look & feel)
2 = minor release
(noticeable changes to functionality or look & feel)
3 = hotfix
(immediate bug fixes; resets to zero on subsequent minor release)
- In consultation with the customer, a list of features and bugs to work on for the week is established.
- This list of features and bugs is grouped together and given a version number like 1.1.0.
- Features and bugs in a version number may only be removed in certain cases:
- In consultation with SAIT - and if the item has not been worked on yet - the customer may remove an item if it should not be in the next release. The customer is obligated to record this removal in Redmine; a phone call or email notification should also be made to inform SAIT.
- In consultation with the customer, SAIT may remove an item if there is not enough time to get it ready for release. SAIT is obligated to record this removal in Redmine; a phone call or email notification should also be made to inform the customer.
- Friday afternoons at 4:00pm, SAIT holds a weekly change management meeting in the SAIT bullpen in the Student Development building. Customers are strongly encouraged to attend this short meeting.
- Current version being worked on is reviewed to ensure all features and bugs have been completed to the customer's satisfaction.
- Current version being worked on is either held back, or approved for release to production the following week during SAIT's regular release window.
- Approved version is pushed to production the following Wednesday night during SAIT's regular release window (10:00pm - 12:00am)