Stay on top of email received on the Release Managers mailing list. This includes for example failure notifications for Jenkins jobs.

In the beginning of your shift

  • Check the Mozilla release calendars:
  • Send the release schedule to tails-dev@boum.org and tails-l10n@boum.org.

    • Ask the core team and contributors for availability at the designated dates for testing the RC and final image.
    • Ask tails@ for a Trusted Reproducer who will reproduce the ISOs and IUKs for the RC and final release within 72 hours after the RM has unplugged their smartcard. When accepting the offer, the Trusted Reproducer must read the ?"Preparation" section of the instructions.
  • Update calendar accordingly.

  • Update the due date on roadmap accordingly.
  • Ask to be added to the rsync_tails group on rsync.lizard, if needed.
  • Make sure you have access to the various systems used to do the release.
  • Check when our OpenPGP signing key expires. If that's before, or soon after, the scheduled date for the release after the one your shift is about, then shout.

Two weeks after the beginning of your shift

  • Ensure you have found a Trusted Reproducer and write who this is in the calendar.

The Friday before the release date

We need to coordinate our Tails release with the Tor Browser developers to make sure that the Tor Browser we plan to include in our release is ready in time for when we build the release image. The Friday prior to the release seems like a good candidate, since it's around this time they usually release tarballs for testing, and it will still give some time for us to improvise according to their "delayed" schedule and arrange a contingency plan (e.g. possibly delaying our release a day or two). Asking for a status report a day or two earlier than Friday in addition won't hurt, too.

Note: Georg Koppen, a Tor Browser developer, has promised to try to Cc tails-dev@boum.org when sending QA requests to tor-qa@lists.torproject.org which should make this easier. We should also be notified of any last last-minute rebuilds that we otherwise probably would miss out on.

See the Upgrading the Tor Browser page for details.

At least for the first release of the year

Have a look at scenarios or features added or modified since last time this check was done, and check if the ones that depend on the documentation have the @doc tag.

Make the release happen

No kidding. See release process.


The release manager shifts could be done by a team. They start right after the publication of the previous release to the publication and announcement of the release they are taking care of, which should be 6 weeks long if everything goes fine.