On Tuesday, August 31, 2010 17:39:11 Jesse Keating wrote:
On 8/31/10 6:57 AM, Michal Hlavinka wrote:
> there's no reason why 1.8 won't be ok after 2-3 weeks in updates-testing
An update that changes behavior for the end user would never be
acceptable as an update to a stable release. Only severe exceptions
should be made to this rule, where the time/effort to backport the
important fixes from a new upstream release are cost prohibitive and too
complicated to do on our own.
I don't thing there is so much updates that change behaviour, see firefox,
thunderbird, kopete, .... usually there are only new features with old
functionality intact. What I wrote was not a rule, there is always a lot of
space for maintainer's decission.
rawhide is not to F-n as debian unstable is to debian testing.
F-n is not to F-(n-1) as debian testing is to debian stable.
no, but I think rawhide is to F-n as debian unstable is to debian stable. What
I wrote as an example was expecting all versions in F-x are stable not that
one version is more stable than another one. That delay was only for being
"really sure" package is stable, because there are not too much users testing
updates-testing packages if it's not new firefox/kernel/... but after a two
weaks in F-n any package is tested quite well