Patrice Dumas wrote:
Since we cannot give a definitive time period, because it is volunteer
based, it is better not to give one.
It is possible for volunteer based projects to give a better timeframe
than merely a ad-hoc maintenance policy. We need to do this in a more
organized way for end users to take advantage of this. If say the kernel
or ssh isn't maintained and has security issues, would it really be
useful for some of the other core packages to get updates?
For two releases and a month (approx 13 months), we do the full updates as
we are doing currently. For another say 5 months or till the next release
we do only security fixes and very major bug fixes (as in crashes all the
time sort of bugs). We don't necessarily backport or guarantee ABI
We don't have the manpower for that.
How do we really know that? I don't think anybody has really looked at
the man power required for doing just critical security fixes for a few
months more.
Rahul
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
