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 enabled
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.
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 r
I am using Rawhide, so I personally don't care. 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.
Vít
Dne 17.2.2018 v 23:15 Zbigniew Jędrzejewski-S
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
> 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
> 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, I agree with Fabio that it
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 delayed up to a we
> 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 Oliver
On Sat, Feb 17, 2018 at 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 d
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 anecdotal
evidence, and
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.
Batching is now the
11 matches
Mail list logo