Release Process

Here's how we tag and build a new release of OneBody:

1. Update the VERSION file in the root of the repo with the new version number.

2. Update the RELEASES.md file in the root of the repo with a broad overview of features and bug fixes, and (if applicable) any release-specific upgrade instructions. (I usually use git log previous..HEAD --oneline to see list of all changes.)

3. Update the version number in the packer config in build/packer.json so that the Amazon AMI has the proper name.

4. Commit with the message "Release x.y.z" (where x.y.z is the version number).

5. Tag the release:

   git tag x.y.z -m "Release x.y.z"

6. Push to GitHub:

   git push
   git push --tags

7. Point the "stable" tag to the latest tag:

   git tag -d stable
   git push origin :stable
   git tag stable
   git push --tags

8. Update the release on GitHub with changes you put in RELEASES.md:

9. Build the OVF:

   cd build
   packer build -only=virtualbox-iso packer.json
   cd output-virtualbox-iso
   zip onebody-x.y.z-1.zip onebody-disk1.vmdk onebody.ovf
   rsync -avzP --bwlimit=30 onebody-x.y.z-1.zip [email protected]:/var/www/statics/downloads.church.io/

10. Build the AMI:

    AWS_ACCESS_KEY=your-access-key AWS_SECRET_KEY=your-access-secret packer build -debug -only=amazon-ebs packer.json

    Make both of the resulting AMIs "public".

    Copy the AMI identifiers and update the Amazon AMI wiki page.

11. Update the latest version number on the following wiki pages:

    • Manual Installation
    • Installation with Docker

12. Announce on:

    • Twitter
    • Google Group
    • Slack topic (optional)

13. Update VERSION file with next version + -pre, e.g.:

    x.y.z-pre
    

    ...and commit to master.