Re: to batch or not to batch?

2018-02-20 Thread Zbigniew Jędrzejewski-Szmek
On Mon, Feb 19, 2018 at 04:02:56PM +0100, Kalev Lember wrote: > On 02/19/2018 03:40 PM, Randy Barlow wrote: > > On 02/19/2018 06:34 AM, Vít Ondruch wrote: > >> But anyway, why don't we > >> have "updates-testing", "updates-batched" and "updates" repositories? > >> "updates-batched" could be

Re: to batch or not to batch?

2018-02-19 Thread Kalev Lember
On 02/19/2018 03:40 PM, Randy Barlow wrote: > On 02/19/2018 06:34 AM, Vít Ondruch wrote: >> But anyway, why don't we >> have "updates-testing", "updates-batched" and "updates" repositories? >> "updates-batched" could be enabled by default while "updates" could be >> enabled manually if one wishes.

Re: to batch or not to batch?

2018-02-19 Thread Randy Barlow
On 02/19/2018 06:34 AM, Vít Ondruch wrote: > But anyway, why don't we > have "updates-testing", "updates-batched" and "updates" repositories? > "updates-batched" could be enabled by default while "updates" could be > enabled manually if one wishes. When we talked about this in the past I believe

Re: to batch or not to batch?

2018-02-19 Thread Vít Ondruch
Vít Dne 17.2.2018 v 23:15 Zbigniew Jędrzejewski-Szmek napsal(a): > Bodhi currently provides "batched updates" [1] which lump updates of > packages that are not marked urgent into a single batch, released once > per week. This means that after an update has graduated from

Re: to batch or not to batch?

2018-02-18 Thread Zbigniew Jędrzejewski-Szmek
On Sun, Feb 18, 2018 at 11:40:47AM +0100, Fabio Valentini wrote: > On Sat, Feb 17, 2018 at 11:15 PM, Zbigniew Jędrzejewski-Szmek > <zbys...@in.waw.pl> wrote: > > Bodhi currently provides "batched updates" [1] which lump updates of > > packages that are not

Re: to batch or not to batch?

2018-02-18 Thread Artur Iwicki
> Batching is now the default, but maintainers can push theirs updates > to stable, overriding this default, and make the update available the > next day. I think that since "batch override" doesn't push the package immediately, but rather schedules it for the next day,

Re: to batch or not to batch?

2018-02-18 Thread Ralf Corsepius
On 02/17/2018 11:15 PM, Zbigniew Jędrzejewski-Szmek wrote: Bodhi currently provides "batched updates" [1] which lump updates of packages that are not marked urgent into a single batch, released once per week. This means that after an update has graduated from testing, it may be

Re: to batch or not to batch?

2018-02-18 Thread Peter Oliver
> Did I miss something on the plus or minus side? + Without batched updates, running “dnf update” gives a variable reward, like clicking refresh on Facebook or playing a fruit machine. Accumulating updates into a batch gives a calmer, more ordered experience. -- Peter Oli

Re: to batch or not to batch?

2018-02-18 Thread Fabio Valentini
On Sat, Feb 17, 2018 at 11:15 PM, Zbigniew Jędrzejewski-Szmek <zbys...@in.waw.pl> wrote: > Bodhi currently provides "batched updates" [1] which lump updates of > packages that are not marked urgent into a single batch, released once > per week. This means that after an

Re: to batch or not to batch?

2018-02-17 Thread Jerry James
On Sat, Feb 17, 2018 at 3:15 PM, Zbigniew Jędrzejewski-Szmek wrote: > Did I miss something on the plus or minus side? Or some good statistics? I thought that was a pretty good summary of the ups and downs. Thank you for that. I have no statistics. But you also asked for

to batch or not to batch?

2018-02-17 Thread Zbigniew Jędrzejewski-Szmek
Bodhi currently provides "batched updates" [1] which lump updates of packages that are not marked urgent into a single batch, released once per week. This means that after an update has graduated from testing, it may be delayed up to a week before it becomes available to users. Batch