Releasing Tracks

These steps are for maintainers with commit access.

1. (Major release only) Make sure documentation is up to date in master. Don’t change the version number yet!
   • /README.md
   • everything in /doc
2. (Major release only) Pin all gem versions using pessimistic version constraints matching the current Gemfile.lock
3. Update version numbers and check copyright dates
   • /README.md
   • everything in /doc
   • /config/initializers/tracks.rb
4. (Major release only) Push new branch to upstream:
   

   git push upstream 2.0

5. Tag the release:
   

   git tag -a v2.0
   git push upstream --tags

6. Create release in GitHub, adding a description of the changes.
7. (Major release only) Update the version numbers in master to the next development milestone
   • /README.md
   • everything in /doc
   • /config/initializers/tracks.rb
8. Build and push the new version to Docker Hub (also to latest and master):
   • docker build -t tracksapp/tracks:2.5.2 .
   • docker push tracksapp/tracks:2.5.2
9. Publicize the new release
   • Post on the Tracks website
   • Update the IRC and Matrix topic
   • Email the mailing list
   • Post to Twitter and Mastodon