On Tue, 2009-06-23 at 23:46 +0100, Adam Williamson wrote: > The problem with this method is it involves a bit more work, because you > can't just send the exact same build to Rawhide and to a stable release > together. I suppose it might also be a bit tough to police > automatically: MDV updates are gatekeeper-ed by the security team, so > this is policed manually there (if you don't version your candidate > update package properly, it doesn't get sent out as an update, and you > get an email telling you what you did wrong). ..and the obvious third problem that this doesn't help when you ship a new version of the package as an official update, of course. In that case you can still get bitten by the 'old' release updates being newer than 'new' release media case. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
