Re: Changes Policy & Fedora Release Life Cycle - request for review

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Nov 10, 2017 at 11:18 AM, Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote:
And, on a even bigger note, the F27 July-to-October experiment worked reasonably well (with the large remainer of the still-outstanding Modular Server) but I don't think we want to do that again. I'd like to suggest that if the April/May release slips into July, or the October/November release slips into January, we *automatically* skip the next target date for a _longer_ cycle to bring us back to schedule rather than a short one.

I thought it worked quite well. If a release gets delayed to July and we completely skip the October release, so that the next release is in April/May, then we need to be willing to push out major version upgrades to the current stable release, and accept any accompanying breakage. And that really blows up the entire concept of having stable releases. A 10 month release cycle seems like a much bigger change to me than a four month cycle. Fedora can't be a year behind and remain relevant.

Michael
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux