Re: Two more concrete ideas for what a once-yearly+update schedule would look like

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



To necromance this old thread, I wanted to give a heads up that we're about to get a cool feature in Bodhi in response to this thread:

https://github.com/fedora-infra/bodhi/pull/1678

With that pull request, there will be a new request state called "batched". When non-priority[0] updates reach the karma threshold, they will go into request:batched instead of request:stable (they will remain status:testing). Once a week, a cron script will look for all updates in the batched state and will switch them all the request:stable. Then they will continue on as they do today. This should help us to reduce the daily churn of Fedora updates for end-users to only be updates they truly need. It may also make the masher be a little faster on 6 days of the week (and slower on one ☺).

There will still be a little more polish work to do after that pull request is merged. For example, for non-autokarma updates we want to change the "push to stable" button to be "push to batched".


[0] The code considers two things to determine whether the update is priority or not: security updates are high prioritity, and urgent updates are considered high priority. All other updates are considered "normal" and will go through the new batched workflow.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux