On Tue, Sep 17, 2019 at 9:55 AM Kamil Paral <kparal@xxxxxxxxxx> wrote: > > Considering this, I believe it makes sense to move the current criterion from Beta to Final. > I'd be okay with letting the responsible team specify a buffer they're willing to accept for Beta (e.g. so Workstation might say "we can allow 10% over our specified limit" and Server can say "if we go over the DVD won't burn, so what's the point?") In other words, any overage would be an automatic blocker, but teams can optionally pre-approve exceptions. This way, teams can still make determinations that are in the best interests of the deliverable they're targeting, but we don't end up in a position we're slipping a week because a deliverable is 5 bytes larger than desired. I like this approach better than just moving the criterion to Final because in cases of large overages, the package gymnastics that might be required to make it work could prove to be pretty impactful. I'd have a lot more confidence in our ability to deliver a good experience to our users if we're trying to trim half a gig from an image before Beta than if we're doing it on the Monday before Go/No-Go. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-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/test@xxxxxxxxxxxxxxxxxxxxxxx
