On Wed, 2019-08-14 at 14:26 -0600, Chris Murphy wrote: > Another option here, is applying the last minute blocker to the > Release Target #1 week, and not to the Preferred Target week. Of even, > if it's a 3 day period apply it to the Preferred Target week; and if 7 > days apply to Target #1 week. Hmm, that's an interesting point, I was kinda ignoring the whole 'preferred target' malarkey with this policy. Indeed the go/no-go meetings are at least initially scheduled in relation to the 'preferred target' dates. Still, I don't want to go making the policy more complicated again... Hmm. Since we've had a proposal for 7 days and a proposal for 3 days, why not just split the difference and say 5 days? That would be the Saturday before go/no-go: so anything proposed the week before isn't covered, but from the weekend on, we're in 'last minute' territory. How does that sound? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ 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
