On 06/13/2017 08:43 AM, Matthew Miller wrote: > On Tue, Jun 13, 2017 at 03:10:58PM +0100, Peter Robinson wrote: >>> This has been due to a variety of bugs and issues, along with pungi now >>> failing composes that don't have all required release blocking items. >> >> Is there a way we can loosen that up for rawhide and have it tightened >> down for branched. I think it's worth while to have at least a flow of >> the everything repository out on a regular basis like the old pre >> pungi-4 use to do. > > I know we're already at new-deliverable explosion, but this seems like > a place where it'd be nice to have Rawhide and Bikeshed (or whatever we > want to call "tested and believed-to-be basically functional Rawhide"). (Side note: I am not sure why we can't just make these the same thing... ie, always have rawhide basically functional). > That doesn't seem imminent, though, so Peter's suggestion seems > reasonable. Then maybe we could ask Jan as FPgM to keep track of what's > working and what's broken and help make sure the right people are on > it. Well, it's sometimes not easy to tell where something is broken, it takes a human to look and dig around and see where the failure is. Example: Today's rawhide compose I had hopes for failed. Turns out it was a koji bug we already fixed and we didn't hit it yesterday because we didn't have the same fixed koji version on all the builders. It took me and Patrick a while to track down what was happening there. There's also another compose running now. Fingers crossed. :) kevin
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
