On Thu, Oct 5, 2017 at 10:14 PM, Randy Barlow <randy@xxxxxxxxxxxxxxxxxxxxx> wrote:
Greetings fellow Fedora friends!
bodhi-2.11.0[0] has been deployed to production, and this release
introduces a new state for updates where the request can be "batched".
The purpose of this state is to give updates a place to sit once they've
reached the stable requirements until the next weekly batch update push.
There is a cron that is set to run on Tuesday's at 03:00 UTC that will
switch all "request: batched" updates to "request: stable"
automatically, and they will then proceed the next time releng does a
push each week.
I know this was a bit controversial when discussed here in the past, so
take solace in this: you (the developer) can override this easily, by
either clicking "push to stable" or by using the CLI to request stable,
just like you do today. The new batched state is just a default state
for updates to go once they hit the karma threshold. In other words, if
you want your update to go out immediately, that's your decision.
So if the update doesn't use karma autopush, and the maintainer clicks "Push to stable", will this go to batched queue or directly stable? And if directly stable, is there a way to put it into the batched queue for such updates?
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
