On Thu, Aug 3, 2017 at 4:45 AM, Kevin Kofler <kevin.kofler@xxxxxxxxx> wrote: >> On Wed, Aug 2, 2017 at 2:47 PM, Matthew Miller wrote: >>> 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). > > Jan Kurik wrote: >> Checking the scope of the F27 [1] I see one more Change "Graphical >> Applications as Flatpaks" [2] we might want to release asap. At least >> I see this Change as a strategical one. > > All these are major infrastructure changes that affect the whole distro and > should not be rushed. They are also changes that bring little to no benefits > in terms of actual new features to our users, they just get to choose > different ways to obtain the exact same software (if they so wish). So those > are completely the wrong things to focus on in a 3-4-month cycle. This is going to follow the Change process, so if at certain point in time the Change will not be ready it will go to FESCo to review the progress and weight risks and benefits of the Change. It is then up to FESCo to decide. Anyone from the Fedora community can join FESCo meetings and express his/her concerns about any Change. You might see risks others do not see, so you can try to describe those concerns to FESCo providing them with broader information to make qualified decision then. > And no-more-alphas is kinda forced by the aggressive F27 schedule, as there > is just no time for an alpha in it! This means the Alpha has to be skipped > no matter whether the tools are actually ready for that. That is also very > risky planning. No-more-alphas is not forced by F27 schedule. It is a goal we were talking about for some time (there were realistic discussions at least from the time of F23 release). The infrastructure is getting ready for it step by step, i.e. development of new "pungi" allowing us to do nightly builds, the development and enhancement of automated CI pipeline (Taskotron, OpenQA) etc. were prerequisites for the No-more-alphas Change which were put in place before we decided to skip the Alpha. I see your point and I agree that due to slip of F26 for five weeks we are in the pressure for F27, but it has nothing to do with the No-more-alphas Change. We were aiming to implement this Change for a long time. Regards, Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
