That's exactly question I had in mind, thanks for bringing it up! Personally, if we won't be able to push breaking changes in F30, then after some time people will not be happy about outdated software and will leave distribution I think.
For maintainers it would probably mean that F29 won't get any updates very soon and they would have to switch to rawhide. On Tue, Nov 27, 2018 at 4:49 PM Owen Taylor <otay...@redhat.com> wrote: > > One of the key parts of making a decision to delay/skip F31 is > figuring out, ahead of the decision, what the expected experience is > for users and packagers. Does F30 have normal stability, or do we try > to keep users happy by moving things forward with ad-hoc updates and > cross-our-fingers and hope nothing breaks? > > I tend to think about this in terms of GNOME - would we rebase to > GNOME 3.34 in the middle of F30 or not? But there's a lot of other > pieces of software where similar considerations apply: container > tools, cockpit, NetworkManager, etc. > > And if we did do updates like that, would we consider respinning media > and making a "F30.1"? > > Owen > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
