Release a pretalx version

You are a pretalx maintainer and want to release a new version? Hold on to your fancy hat or your favourite socks, here we go!

Boarding checks

  1. Are the translation files up to date?

  2. Are there pending checks for bad translations on Weblate?

  3. Are there pending translations from Weblate? Merge them.

  4. Are all locales with more than 75% coverage included in the release? If new translations need to be added, add new calendar locales (you have to download the release archive) and extract the locales from there), and make sure that flags (in input fields) for the new locale are shown.

  5. Are there warnings about missing migrations?

  6. Any blockers to see in our issues?

  7. Are there any TODOs that you have to resolve?

  8. Are there any @pytest.mark.xfail that you have to resolve?

  9. Are the Release Notes well-phrased and complete?

  10. Are there open pull requests that you should merge?

  11. Are all tests passing in CI?

  12. Have you written (and not pushed) a blog post? It should contain at least major features and all contributors involved in the release.

System checks

  1. Deploy the release-ready commit to an instance. Check if the upgrade and the instance works.

  2. Clean clone: git clone git@github.com:pretalx/pretalx pretalx-release && cd pretalx-release (or local clone)

  3. Run just release-checks locally.

Take-off and landing

  1. Run just release v202X.Y.Z

  2. Install/update the package somewhere.

  3. Publish the blog post.

  4. Upgrade the docker repository by running just release v202X.Y.Z

  5. rm -rf pretalx-release

  6. Update version numbers in update checker (versions.py) and deploy.

  7. Update any plugins waiting for the new release.

  8. Check if the docker image build was successful.

  9. Post about the release on chaos.social, Twitter and LinkedIn.

  10. Notify interested parties (e.g. big self-hosted instances, prominent plugin developers) about the release.