+++ This bug was initially created as a clone of Bug #1397688 +++ +++ This bug was initially created as a clone of Bug #1397684 +++ Staged rolled is turned back on after merge day. This means we push beta to 10% of our user base, until a human manually increases the number or push to the "production" track. Release Engineering needs to agree with Release Management about when we want to push beta to 100% of our user base without any human action (and no possibility to unpublish the beta). Once both RelEng and RelMan agreed, RelEng should land the opposite patch of bug 1358420. This has to be manual, while both RelMan and Releng agree on the automation strategy (bug 1397679).

It looks like this is configured in https://dxr.mozilla.org/mozilla-central/source/taskcluster/ci/push-apk/kind.yml now.

julien: what would you like to do here. We missed this for the chemspill but going forward in 59, do we want to disable staged rollout?

Yes, I think we're ready to move to 100% on 59 beta. Yesterday, I set it to 99.99% manually for 59.0b5 and there are no crashes that block rolling out to all users.

Based on https://reviewboard.mozilla.org/r/137442/diff/1#index_header, this looks like what we want. I'm not exactly sure why rollout-percentage should be null instead of 100.

Comment on attachment 8946729 [details] [diff] [review] change fennec to 100% rollout Review of attachment 8946729 [details] [diff] [review]: ----------------------------------------------------------------- I'm assuming this needs to be uplifted to m-b? Wee, in-tree configs.

(In reply to Jordan Lund (:jlund) from comment #6) > Comment on attachment 8946729 [details] [diff] [review] > change fennec to 100% rollout > > Review of attachment 8946729 [details] [diff] [review]: > ----------------------------------------------------------------- > > I'm assuming this needs to be uplifted to m-b? Wee, in-tree configs. Yep!

Comment on attachment 8946729 [details] [diff] [review] change fennec to 100% rollout https://hg.mozilla.org/releases/mozilla-beta/rev/7ad2f82facfad77f5b94a24e972b3ec021c3ea77 I explicitly didn't land this on inbound or central because it sounds like we always want to start beta at 10% after an uplift. As far as I can tell, this means there's no reason to ever change mozilla-beta to 100% on central.