On Fri, Mar 03, 2017 at 10:21:56AM -0500, Owen Taylor wrote: > * Run the entire Fedora Rawhide compose process out of a cron job, > like the Fedora Atomic Host compose. This would likely require us to > remove Rawhide from the mirrored set, but mirroring Rawhide doesn't > seem important - it is presumably a tiny portion of overall Fedora > bandwidth usage. I agree that separating Rawhide out of the main mirror channel would be relatively low-impact; it's a tiny fraction of the connections every day. We might want to offer a nightly snapshot on an optional mirror channel or something like this. > * Run just the *workstation* Fedora Rawhide compose out of a cron job > - I don't know how separable one edition is from the overall process. Right now, it is very, very tightly coupled. > 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? -- Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> Fedora Project Leader _______________________________________________ desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to desktop-leave@xxxxxxxxxxxxxxxxxxxxxxx
