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 by default while "updates" could be > >> enabled manually if one wishes. > > > > When we talked about this in the past I believe resources were the > > concern, both on the Fedora infrastructure side and on the mirroring side. > > I think a new, additional repo with batched contents should solve a lot > of problems here: we'd have both side of the fence happy (regular users: > batched updates, developers: continuous stream of updates), and it would > also make it possible to actually QA the batched set before it hits the > mirrors. Those are good points. I'd also add that since this removes the reason why developers were overriding batched to push to stable, hopefully we would see more packages go to batched. > Right now there's no way for QA to only extract batched updates without > getting all the rest of updates-testing; if we had that we could > actually have people test the batched set of updates before they are > pushed out to stable. That answer another doubt that people had. Zbyszek > P.S. Those who were at the Atomic Workstation call that ended a few > minutes ago, I believe this is what we need to solve the split updates > problem that we talked about. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
