Tomboy for FC6 not being updated... why?

Christopher Aillon caillon at redhat.com
Thu Jul 12 17:31:05 UTC 2007


Ralf Corsepius wrote:
> On Thu, 2007-07-12 at 09:52 -0400, Jesse Keating wrote:
>> On Thursday 12 July 2007 09:43:08 Jon Ciesla wrote:
>> > My understanding was that updates, both security-related and
>> > non-security-related would continue for F-N until F-N+1 was released.  At
>> > that point, F-N would join F-N-1 in a security-only mode until EOL.
>> > People expect churn on Fedora, so stay on the bleeding edge (not so
>> > bleeding as rawhide, mind you). Is that not correct?
>> 
>> Well, since the old end of life was F-N+2 Test2, we talked about making /that/ 
>> the security only point and the no new packages point.
> Well, IMO, Fedora's purpose should be "stable while following upstream
> without API/ABI breakages of existing packages". 

But we also practice don't fix what isn't broken.  This is one of the 
reasons we don't force mass rebuilds of all packages for each release: 
packages are a known quantity and changing them might fix some bugs but 
break other things.  I get this in Firefox updates all the time, and 
those _are_ security fixes.  I'd bet other packages do as well.

If someone files a bug which happens to be fixed in the latest stable 
upstream, feel free to take the version bump if you think it's right. 
But don't simply assume that users are seeing the bug when the version 
bump can introduce more problems than it fixes (how many times have we 
seen various upstreams make a release only to follow it up with a new 
release the next day to correct "serious problems"?  updates-testing 
helps here, but that assumes that users of your package use 
updates-testing which we cannot guarantee).




More information about the fedora-devel-list mailing list