On Wed, Aug 02, 2017 at 01:24:21PM +0200, Kevin Kofler wrote: > It is really sad that FESCo is still maintaining this completely unrealistic > kamikaze schedule. We have seen from the fallout of the mass rebuild that > this is absolutely impossible to hold, the release will be completely broken > that way. > > There need to be at least 6 months from the Fedora n release (the ACTUAL > release, not the planned one) to the Fedora n+1 release, or there is no time > to do development or even bugfixing. The schedule has less than 4 months. It > should be obvious that this cannot possibly work. It's going to be a challenge but I think we can do it. I don't think sliding around the calendar (as actual release date + six months causes) is good either — in fact, I think overall it is worse. Because it is a short release, we should focus on a few key changes and otherwise limit scope as much as possible. From my perspective, the things we should focus on this time around are infrastructure related: - enabling CI for Atomic Host, including the Pagure front-end and PR workflow - modularity stuff for Fedora Server (and, because of the timeframe, definitely scoping that to Server and not the whole distro) - validation test automation and the no-more-alphas project. Collectively, are there other F27 changes that seem really key to release this year? If possible, I'd like to target any bigger changes for F28 (or, unlink them from the release itself). And, remember, the other side of this scheduling plan is that F28 should definitely come in May (and ideally early May). If we followed the sliding plan, we'd be targetting F27 at January, releasing it in March, and having F28 next December. -- Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> Fedora Project Leader _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
