On Fri, 2009-05-08 at 06:05 +0200, Ralf Corsepius wrote: > 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"). I eventually do want to have the ability for maintainers to self service buildroot overrides. We just don't have the code in place, nor enough people to work on the code while we work on other things too. Although while we're trying to finish up a release, I would ask where we should publish the next rawhide, or what you mean by rawhide/testing. > > 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. We're going to be pushing an initial set of F11 updates in the next day or so. > * to prevent NEVR issues resulting from F-9, F-10 and F-12 being open, > while F-11 is frozen. Won't help at all, as the F11 release repo doesn't change, nor do the contents of the DVD, so F9/10 will always move ahead of the release. > > * 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". So you want a rawhide, and a rawerhide? > > 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. We already do that based on maintainers and testers who propose and test packages during freezes. -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
