On Sat, 2017-03-04 at 17:15 -0800, Adam Williamson wrote: > Goal 7 (future) > > > =============== > > > Have a "rolling stable" stream of Fedora that gets major updates > > > not on > > > a six-month-tempo, but after those changes have seen testing in > > > Rawhide. We already treat the kernel like this. > > > > This overlaps a lot with work Adam and Dennis have been doing (see > > https://fedoraproject.org/wiki/Changes/NoMoreAlpha for part but not > > all). Have you talked with them? > > I don't think we've discussed it, no. I think the focus is a bit > different: the NoMoreAlpha thing is about keeping Rawhide basically > functional, really, not about keeping it at a level of quality where > we could call it 'rolling stable'. I don't think anybody expects Rawhide to miraculously turn into "rolling stable" - the first step is to get it to "rolling usable" :-) Hopefully the things I'm proposing here are complementary to the ideas of NoMoreAlpha - in the context of Atomic Workstation, we have the ability to go beyond the package level and actually run integration tests on the actual operating system that the user will be running, and then we can add a second level of gating. Package is build => package tests => package goes into tree => integration tests => tree is tagged for distribution to users The more we catch problems at the first level, the better, but some problems won't be found that way. If we get better at making Rawhide usable, we can decide whether to push forward towards further stability (say by the idea of having devel branches for major changes, and only merging when they are pretty stable), or alternatively use the expertise we've gained to be better at making changes to a stable branch. - Owen _______________________________________________ desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to desktop-leave@xxxxxxxxxxxxxxxxxxxxxxx
