On Tue, Oct 08, 2013 at 03:39:39PM +0000, "Jóhann B. Guðmundsson" wrote: > How are you going about guaranteeing rawhide is always consistent > given different focus and moving parts? More branches, possibly using COPRs. At a high level, revamping our development process to support continuous delivery. > >I think in general (not just anaconda) we_don't_ want development > >happening on "X". That process should be about stabilization and qa. This > >has traditionally been hard because Rawhide is too raw, but we have > >efforts underway to make it less so, and if that solves non-theoretical > >problems we can push harder on those efforts. > Which efforts are those? FUDCon Lawrence and following. See: https://lists.fedoraproject.org/pipermail/devel/2013-March/179337.html -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm@xxxxxxxxxxxxxxxxx> _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
