Release procedure

joe hobson edited this page Sep 25, 2018 · 2 revisions

The general release process is:

  1. Run smoke screens on alpha
  2. 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
  3. Create a new tag for the release in github based on the assigned version number
  4. Download the .zip and tar.gz tags and upload each as a new Latest Stable Release download with the release date in parentheses
  5. Remove the previous Latest Stable Release download links
  6. Release to production nodes
  7. Release to sandbox node
  8. Update the list of known nodes to reflect the release each node is running
  9. Send email describing release to all LR Google groups
  10. Update Linux, Windows, Mac, and AMI install guides to reference new tag
  11. 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.)
  12. Update the list of Current AMI Instances
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.