On Monday 25 June 2007 11:44:07 Jochen Schmitt wrote: > I'm again autopromotion, because is contains the danger, that unstable > package will going > in the update stage. Instead it may be helpful, if you may send a nag > mail, if an update will > stay too long in the update_testing stage. Right now just the idea is approved. Along with that idea would come reasonable mechanics to make it work, such as any user being able to block autopromotion if they find a problem with the package. It's up to releng and QA to come up with reasonable mechanics and boundaries to autopromotion. > From my point of view two other topic may be important: > > 1.) Handling of update chains in koji and bodhi. I have several updates, > where one package > which I have updated is depend on an other package which was submitted > by another > maintainer into the update-testing The current state is, that you have > to contact rel-eng for > assistents in this cases. We've already discussed this. We want buildroots to autoupdate in principle, however we require some sanity checking in bodhi to not allow updates to go out that were built with packages that aren't tagged to go out or out already. > > 2.) There was request for a seperate security_updates repository for F-7. This can be accomplished by the yum-security plugin, once bodhi is capable of generating the extra update metadata. I'm sure Luke would love a hand in getting some of this accomplished. -- Jesse Keating Release Engineer: Fedora
Attachment:
pgpDrtOMh5ofh.pgp
Description: PGP signature
-- Fedora-maintainers mailing list Fedora-maintainers@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers
-- Fedora-maintainers-readonly mailing list Fedora-maintainers-readonly@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly
