182 pending F11 stable updates. WTF?

Ralf Corsepius rc040203 at freenet.de
Fri May 8 04:05:40 UTC 2009

Jesse Keating wrote:
> On Fri, 2009-05-08 at 05:12 +0200, Ralf Corsepius wrote:
>> 1. It already is
>> 2. It doesn't have to be that way
>> IMO, a significant portion of such issues is caused by rel-eng's freeze 
>> and defects in fedora's work-flow.
> The cut images will always remain stagnant, the rpms not changing.  So
> long as we allow updates to previous releases to be n-v-r higher than
> the GA versions of the next release, we will always have a broken
> upgrade path from N-1+updates to N.
> Are you suggesting some distro release level super epoch?

I am suggesting that you implement rawhide/testing, f11/testing and 
f11/updates right now and get rid of "trac" (replace buildroot overrides 
with button in koji or treat "push to stable" as "buildroot overrides").

This would resolve several issues packagers have been facing (and now 
hit you) at once.

In particular would it help
* to prevent packages from queuing up on the packager's side, which 
would have been released very soon/immediately after GA in any case.

* to prevent NEVR issues resulting from F-9, F-10 and F-12 being open, 
while F-11 is frozen.

* rawhide/testing would also help wrt. test rawhide for 
experimental/unsafe stuff, which would help improving stability when 
rel-eng brands a rawhide snapshot "Fedora release".

There would be one major difference: rel-eng, would have to herry-pick 
and move around packages between F11 GA and F11/updates before the release.


More information about the fedora-devel-list mailing list