Commit d6fadd6f authored by intrigeri's avatar intrigeri

Release process: reorder steps

Every time I'm the RM, I'm done with all steps that used to come after this one
before Jenkins has finished building. So let's check this at the end.
parent 8add5880
......@@ -1829,8 +1829,6 @@ If you just released a final release
./bin/apt-snapshots-expiry
1. Push the resulting branches.
1. Make sure Jenkins manages to build all updated major branches:
<https://jenkins.tails.boum.org/>.
1. In [[contribute/calendar]], remove the entries about the version that you've
just released.
1. Check the Mozilla release calendars:
......@@ -1852,6 +1850,8 @@ If you just released a final release
tasks that must be done at the beginning of your shift in the
[[release manager role page|contribute/working_together/roles/release_manager#shift]].
Otherwise, kindly remind the next release manager about this :)
1. Make sure Jenkins manages to build all updated major branches:
<https://jenkins.tails.boum.org/>.
If you just released an RC
--------------------------
......
Markdown is supported
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