How to release Quepid

Quepid is a bit of an odd duck, since it's a hosted application at http://app.quepid.com, and a Docker image available at https://hub.docker.com/repository/docker/o19s/quepid for Dockerized deploys, and of course a straight up Rails app you can install.

So releasing a new version of Quepid requires a number of steps, some that can only be done (today!) by OSC folks.

1. Make sure the CHANGELOG.md is up to date. We like to give credit where possible to contributors, so please list their Github name if possible. Since we are cutting a release, set today's date in the Changelog.

2. Go ahead and create the Release in Github, along with the tag. Copy the relevant section in CHANGELOG.md into the notes.

3. In the Heroku Console, go ahead and promote the most recent Staging Quepid setup to Production. Right now we need to do some extra steps (https://devcenter.heroku.com/articles/git) due to oauth/github/heroku issues. You will need to run any migrations via:

heroku run bin/rake db:migrate -a quepid  # or quepid-staging ;-)
heroku restart -a quepid # or quepid-staging ;-)

4. Tag and deploy production optimized Quepid Docker image using Dockerfile.prod to Docker Hub (https://hub.docker.com/repository/docker/o19s/quepid):

export QUEPID_VERSION=6.0.1   # or add -dev or -test

And run:

docker build --build-arg QUEPID_VERSION_VARIABLE=$QUEPID_VERSION -t o19s/quepid:$QUEPID_VERSION -t o19s/quepid:latest -f Dockerfile.prod .

docker push o19s/quepid:$QUEPID_VERSION
docker push o19s/quepid:latest

5. Update the Chorus Docker Compose script for the new version. This is a great "last chance" option to test the release version of Quepid. Recommended if you have migrations or other setup changes in a release. See the lessons learned from releases 6.3.1.1 and 6.3.1.2 ;-)

6. Make an announcement on Relevance Slack #quepid channel and on Twitter to @quepid_search and on Intercom to Quepid users.