On Mon, Jan 8, 2018 at 5:39 PM, Kevin Fenzi <kevin@xxxxxxxxx> wrote: > On 01/07/2018 08:01 PM, Kevin Kofler wrote: >> Kevin Fenzi wrote: >>> The critera for bypassing batched is if the update is marked "urgent". >> >> The problem is, this appears to be insufficient. > Well, if this firefox update was urgent, shouldn't it have been marked > urgent? I thought for some reason that all updates marked as security were automatically urgent, maybe I'm misremembering, but if not it might be good to do that as a RFE that way all security updates go out non batched. >> I really don't understand why we do this "batched" thing to begin with. > > To reduce the constant flow of updates that are very minor or affect > very few mixed in with the major updates that affect lots of people and > are urgent. To save users downloads of repodata. > >> Users who want to batch updates have always been able to do it, GNOME >> Software will even do it for theNow, those users who want to batch their >> updates are forced to follow Fedora rel-eng's schedule for the batches >> rather than being able to pick their own weekday, so how does the server- >> side batching help them? And those users (like me) who want to get their >> updates, including security fixes (!) as we see here, as soon as they passed >> testing are now screwed. > > rel-eng's schedule is a cron job at 03:00 on tuesday (so the batch > appears on wed's pushes). > > There was some discussion about changing the gnome batching based on the > Fedora batching, but I don't know whats happened there. > > I haven't seen a bunch of urgent updates get blocked by this process. > Do you have more data for updates that hit this? > >> If people insist on that "batched" misfeature, can we please at least get a >> fast track repository that contains all the batched updates (but no updates >> that are still in testing and have not been batched yet!)? > > I would be very much against additional repos like this. > > > kevin > > > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
