Release procedure

This page is for notes about how to manage a release of Querki. As of this writing, I'm about to start releasing frequently, so it's time to get disciplined about it. (And stop having to remind myself how to do it each time.)

In order, the steps for release are:

• Run all automated tests. (Both utst and ftst.)
• In build.sbt, update the appVersion. For now, while things are moving quickly and we are usually adding significant features, you will usually update the MINOR number.
• Check everything in.
• If working in a branch, open and merge a PR.
• Cut a Release in GitHub.
• Make sure the Production Build machine is running.
• Connect to the Production VPN, and log into the Production Build machine.
• goq -- go to /apps/querki/Querki/querki.
• git pull to update the code.
• If config has changed: Make sure that the application config file (scalajvm/conf/application.conf) is up to date: since this does not get checked in, any changes must be manually applied. SAVE THE PREVIOUS VERSION.
• If there have been any evolutions for the database: apply them manually. (As of this writing, the app doesn't have some of the permissions often needed, so evolutions have been disabled on the production system.)
• act to start Activator.
• conduct info to see the state of things. If there is an old not-running build, conduct unload ID it.
• Maybe clean, then compile.
• bundle:dist to build the ConductR bundle.
• conduct load TAB to load the newly-built bundle to the cluster.
• conduct info to make sure it is loaded to all machines.
• conduct stop ID on the currently-running Querki. Pay attention to the messages, to make sure that it goes to scale 0.
• conduct run ID --scale 3 on the new version. Pay attention and make sure it goes to scale 3.
• conduct info to make sure it has started on all 3 machines.
• Sanity-test to make sure things are running.
• Shut down the build machine.
• Post on Querki News.
• Link to the Querki News article on the Querki FB page. (Except for patch releases, which aren't worth spamming the user base over.)