Re: Two more concrete ideas for what a once-yearly+update schedule would look like

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

 



On Tue, Dec 20, 2016 at 10:01:57AM -0800, Gerald B. Cox wrote:
> I'll repost this because I believe Kevin had a good point:
> 
> I don't understand why we are trying to reinvent the wheel here.  The
> infrastructure for Kevin's suggestion
> is in place now - KDE has been using it and it works.

This has the same downside as a rolling release to end users. It asks
them to take a big user interface / user experience update whenever we
push it, or else disable all updates including security fixes and
bugfixes that do not change user experience.

Modularity, however, will allow us to update module stacks — like GNOME
or KDE — while still also maintaining older versions for some time...
without tying the whole release to that cycle.

-- 
Matthew Miller
<mattdm@xxxxxxxxxxxxxxxxx>
Fedora Project Leader
_______________________________________________
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