Bodhi now has a "batched" request state

[Randy Barlow]

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.

Important updates that need to go out immediately (think: bad bug or
important security update) can set the severity to "urgent", which will
skip the batched state automatically.

Let me know if you want clarification about any of this, and happy hacking!


[0] https://bodhi.fedoraproject.org/docs/release_notes.html

[Zbigniew Jędrzejewski-Szmek]

On Thu, Oct 05, 2017 at 04:14:47PM -0400, Randy Barlow 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.
>  
>  Important updates that need to go out immediately (think: bad bug or
>  important security update) can set the severity to "urgent", which will
>  skip the batched state automatically. 
Sounds great. Nice work!

Zbyszek

[Kamil Paral]

On Thu, Oct 5, 2017 at 10:14 PM, Randy Barlow <randy(a)electronsweatshop.com&gt;
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?

[Randy Barlow]

On 10/06/2017 06:18 AM, Kamil Paral wrote:
>  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? 
Hello Kamil!

A non-autopush update will get a "push to batched" button when it
achieves karma or testing time, and I think after it is batched a "push
to stable" button will appear. Or maybe they both appear at first? I
can't recall which way it is, but either way you can push it to batched,
and you can push it to stable too.

[Michael Cronenworth]

On 10/06/2017 01:47 PM, Randy Barlow wrote:
>  but either way you can push it to batched,
>  and you can push it to stable too. 
Except when it was auto-pushed to batched.

https://bodhi.fedoraproject.org/updates/FEDORA-2017-a62dd57720

- Auto-pushed to batched
- No push-to-stable button
- After editing to mark as Urgent, still no push-to-stable button

Am I forced to wait an entire week to let it be pushed out via batch?

[Adam Williamson]

On Tue, 2017-10-17 at 08:44 -0500, Michael Cronenworth wrote:
>  On 10/06/2017 01:47 PM, Randy Barlow wrote:
>  > but either way you can push it to batched,
>  > and you can push it to stable too.
>  
>  Except when it was auto-pushed to batched.
>  
>  https://bodhi.fedoraproject.org/updates/FEDORA-2017-a62dd57720
>  
>  - Auto-pushed to batched
>  - No push-to-stable button
>  - After editing to mark as Urgent, still no push-to-stable button
>  
>  Am I forced to wait an entire week to let it be pushed out via batch? 
You can do stable requests via the CLI, which will let you do it in
various cases where the web UI doesn't offer a button:

bodhi updates request FEDORA-2017-XXXXXXXXXX stable
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

[Matthew Miller]

On Tue, Oct 17, 2017 at 12:56:56PM -0700, Adam Williamson wrote:
>  > Except when it was auto-pushed to batched.
>  > https://bodhi.fedoraproject.org/updates/FEDORA-2017-a62dd57720
>  > - Auto-pushed to batched
>  > - No push-to-stable button
>  > - After editing to mark as Urgent, still no push-to-stable button
>  > Am I forced to wait an entire week to let it be pushed out via batch?
>  You can do stable requests via the CLI, which will let you do it in
>  various cases where the web UI doesn't offer a button:
>  
>  bodhi updates request FEDORA-2017-XXXXXXXXXX stable 
And after using that workaround for now, sounds like the above case is
a pretty good RFE.

-- 
Matthew Miller
<mattdm(a)fedoraproject.org&gt;
Fedora Project Leader

[Randy Barlow]

On 10/17/2017 09:44 AM, Michael Cronenworth wrote:
>  On 10/06/2017 01:47 PM, Randy Barlow wrote:
> > but either way you can push it to batched,
> > and you can push it to stable too.
>  
>  Except when it was auto-pushed to batched.
>  
>  https://bodhi.fedoraproject.org/updates/FEDORA-2017-a62dd57720
>  
>  - Auto-pushed to batched
>  - No push-to-stable button
>  - After editing to mark as Urgent, still no push-to-stable button
>  
>  Am I forced to wait an entire week to let it be pushed out via batch? 
Hi Michael!

This is definitely an unintended bug, so I've filed it for you:

https://github.com/fedora-infra/bodhi/issues/1907

I do believe the CLI would allow you to push this one to stable as a
work around as suggested by Adam.

[Randy Barlow]

On 10/17/2017 05:53 PM, Randy Barlow wrote:
>  I do believe the CLI would allow you to push this one to stable as a
>  work around as suggested by Adam. 
To make it easy for you, the bodhi-2 CLI command to do this is:

$ bodhi updates request FEDORA-2017-a62dd57720 stable

If you are on Fedora 25 (which has bodhi-0), you can get bodhi-2 from my
Copr:

https://copr.fedorainfracloud.org/coprs/bowlofeggs/bodhi/

[Michael Cronenworth]

On 10/17/2017 04:53 PM, Randy Barlow wrote:
>  This is definitely an unintended bug, so I've filed it for you:
>
>  https://github.com/fedora-infra/bodhi/issues/1907
>
>  I do believe the CLI would allow you to push this one to stable as a
>  work around as suggested by Adam. 
Thank you. The CLI worked.