On Tue, 2017-06-13 at 22:47 +0100, Peter Robinson wrote: > > > > > Greetings. > > > > > > > > > > Some folks may have noticed that there have been no completed > > > > > rawhide > > > > > composes in a while (13 days as of today). > > > > > > > > > > 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. > > > > > > Possibly yes. But I think the idea was to do it for rawhide as > > > well and > > > thus always be at least "Alpha" quality so we could not do alpha > > > anymore. > > > > That was my take on the "no more alphas". If we can't do this then > > we > > are going to have to look at doing an alpha in the schedule because > > it > > is clear we aren't able to stabilize enough for that promise to > > exist. > > For actual artifacts such as cloud/disk/installer images I agree but > at least pushing out individual packages so people can do "dnf > upgrade" picks up issues such as dependency issues that also kill the > compose and allows people to still test explicit parts and have the > composite parts of a "rolling release" and get things fixed.... I > feel > that's better than dragging everything to a blinding halt like we > have > for the last 13... or is it 14 days? > > I can't help but feel this is like British politics is ATM where > people are claiming everything is "strong and stable" while the > wheels > have fallen off and are rolling down the road. I don't think pushing > out the Everything repo stops the "kill off Alpha" process from > happening, in fact I believe it means it's more likely to happen > because if the last two weeks shows anything all that happens is that > if we wait for a "everything is perfect ship it" we never will and > because nothing is shipped nothing is tested I agree with that - for example the Anaconda installer CI broke due to a rawhide package change in the last "working" compose. There is a fixed package available and built in Koji, but it's not reaching the Rawhide repos due to the broken composes. In this case we can fix the CI by using a COPR build of the package, but in other cases it could be more difficult. BTW, when was the change to only release packages to repositories once a compose succeeds introduced ? I kinda always thought packages go to the Rawhide repos almost immediately - mirroring machinery permitting. > so once we get to the > "computer thinks it's good" we can get to the actual testing and then > we get to "what the hell changed in the last two weeks broke X, Y and > Z, are they related or completely independent?" process. > > I think the all or nothing actually makes it less likely for us to > ever ship anything! I don't think shipping the traditional > "Everything" repo breaks the "kill Alpha" proposal, I think we need > to > be pragmatic and realise that people actually consuming content helps > that. > > Peter "yes I live in the as strong and stable as a house of cards > country so I can joke/comment on it" R > _______________________________________________ > 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
