On Mon, 2015-12-07 at 20:19 +0100, Michael Schwendt wrote: > On Mon, 7 Dec 2015 10:53:32 -0700, Kevin Fenzi wrote: > > > So, what you would like would be: > > > > a) If you have autokarma set and the update doesn't reach autokarma, > > push it automatically when it reaches the timeout. > > With a customisable timeout, it would be a good feature. > > > b) Have another bodhi setting for 'push automatically when reaching the > > 'maintainer can now push to stable' time limit. (defaulted on or off?) > > Not so good, because the current blocking period seems arbitrary. > 14 days? 7 days? Why? It's a rather short period (considering that it > can take days for a mirror to pick up new packages) and doesn't give all > testers enough time to notice the test update and test it painstakingly. It's a trade-off between people who want to be able to push updates out promptly and people who want to ensure sufficient testing. It's never possible to get a 'perfect' policy when dealing with the range of packages in Fedora; no setup is ideal for *all* of them. All our policies are trade-offs. It shouldn't ever take 'days' for a mirror to pick up new packages. Any mirrors that slow should be dropped from the mirror list, I think. The timer starts from when the update is *pushed* to testing (i.e. when it actually gets there on the master mirror), not from when the maintainer *submits* it, so the delay that can occur between an update being submitted and being pushed is not counted in the required wait time. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
