The primary concern I had around this was - I want to make something that "early adopters" could test and provide feedback on, but *also* run seriously. By "seriously" for example I mean we need security updates, and we need at least one "stable" branch where things aren't churning too much for the base OS. So having the project *solely* linked to rawhide doesn't really meet those criteria today. If we have both f26 and rawhide branches that seems OK. But I also want the ability to quickly test changes to the f26 version (same requirement for Atomic Host actually) - be able to quickly pull in a testing version of e.g. systemd or anaconda that *don't* affect things derived from the "base package set". _______________________________________________ desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to desktop-leave@xxxxxxxxxxxxxxxxxxxxxxx
