On Tue, 2019-08-13 at 23:36 +0200, Kevin Kofler wrote: > Adam Williamson wrote: > > It's not really about "accountability", it's simply: we can only really > > assume the package is being tested once it makes it to the repo. Yes > > you can pull it out sooner manually or using bodhi CLI, but very few > > people do that. The intent of the rule is "we want people to have 7 > > days to test out the update and make sure it's OK". > > Then complain to rel-eng or infra if they waste your testing time. :-) > It is still not fair to maintainers to make them wait up to 10+ days from > submission until they can push their update to stable because of some > infrastructure breakage that is no fault of theirs. But the key principle here isn't 'fairness', it's 'is the package broken'. That's the actual thing we're trying to achieve. From that perspective it doesn't make any sense to start the timer on submission rather than push. The best way to avoid the problem you identify is to make the updates pushes faster and more reliable. -- 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 To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
