Commit 6dbd9f55 authored by intrigeri's avatar intrigeri
Browse files

Release Manager: make some expectations explicit.

The goal is to avoid issues such as #15400: Jenkins had been telling us for
48 hours that the testing branch did not build reproducibly anymore,
but the release manager missed that, built a tentative 3.6 ISO and decided
to release it as-is.

refs: #15400
parent f87f39ae
......@@ -80,6 +80,12 @@ be `testing` for major releases, and `stable` for point-releases.
Read the remainder of this document from the branch used to prepare the release!
Sanity check
Visit the [Jenkins RM view](
and check that the jobs for the release branch have good enough results.
......@@ -2,6 +2,11 @@
# Tasks
## Continuously
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:
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment