El mar, 07-03-2017 a las 10:26 -0500, Owen Taylor escribió: > On Tue, 2017-03-07 at 08:30 -0600, Dennis Gilmore wrote: > > El vie, 03-03-2017 a las 11:30 -0500, Matthew Miller escribió: > > > 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. > > > > Atomic host in rawhide is not done as a separate compose its all > > part > > of the one rawhide compose. > > I move have misunderstood. So there is no Atomic Host ostree creation > that happens more than once a day? There is no Atomic Host compose that happens more than once a day currently. We do a daily one for latest stable fedora and we build all the pieces as part of rawhide. we have a ostree that we continuously update, it is however only a ostree, we could do workstation ostree as well > > > > > 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? > > > > > > > Honestly the best thing you can do to get it working, stable and > > better right now is to have people be engaged, paying attention, > > testing and fixing issues, the workstation ostree pieces have been > > failing to compose for months, as its non blocking Releng does not > > look at it at all as we have too many other things going on. You > > and > > your team have to get engaged and work on it if you want it to > > change > > and be something going forward > > Asking people to fix one thing a day then recontext-switch into the > task the next day is incredibly discouraging to getting things > working. > So, for now, let's concentrate on goal one: how do we get a > workstation > ostree built more than once a day? What needs to happen to enable > that? I am just asking you to work with us, pay attention and fix the things that have been failing for months with no one looking at it. Step one is getting it built once a day, because that does not happen. and has not in ages. Dennis _______________________________________________ desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to desktop-leave@xxxxxxxxxxxxxxxxxxxxxxx
