forked from LearningRegistry/LearningRegistry
-
Notifications
You must be signed in to change notification settings - Fork 2
Release procedure
damonregan edited this page Jan 24, 2012
·
10 revisions
The general release process is:
- Run smoke screens on alpha
- Define the version number for the release based on the version of the spec the code best aligns with and the current iteration of code WRT that spec
- Create a new tag for the release in github based on the assigned version number
- Release to production nodes
- Release to sandbox node
- Send email describing release to all LR Google groups
- Update Linux, Windows, Mac, and AMI install guides to reference new tag
- Update or create a new AMI to include the new LR code (For instructions on doing so, please refer to this document. When creating or updating an AMI, please use the current tag as the AMI name.)
- Update the list of Current AMI Instances