On Wednesday 20 December 2006 11:35, Bruno Wolff III wrote: > Doesn't that work still need to eventually get done in any case? The fixes > will need to be done before the next release. Maybe there is some time > savings in not worrying about things until the next release and handling > all of the issues at once? There is a difference though between fixing it in the devel branch where things could be vastly different, and fixing it for the released branch, where things haven't been changed at all. Now you have to come up with possibly two different ways to fix things, three if you consider the N-1 release. > I wouldn't think the extra work would be all that much, anaconda doesn't > have all that many dependencies and they are typically things you guys > don't muck with a lot until the next release anyway. You wouldn't think so, but those who have _done_ this kind of work _know_ that it is a lot of extra work, for folks who have very limited time to get the new stuff done that is expected of them. > I don't see updates.img as all that great of a solution. There is about > 2GB of FC6 updates already (though this includes some cases of multiple > updates). Currently there probably are only a few people even trying to > do respins, but with the merging of core and extras I expect there to be > more people who want to do custom respins. Respin attempts can happen, but when the new package set + anaconda fails, who's going to do the work to fix things? -- Jesse Keating Release Engineer: Fedora
Attachment:
pgpORdt2HHvFs.pgp
Description: PGP signature
-- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list