On Wed, Aug 14, 2019 at 1:26 PM Adam Williamson
If we say 3 days, then we're committing to doing all of that for a
blocker that's proposed the Sunday before the go/no-go - one day before
the final blocker review meeting. Which, I mean...yeah, we have time to
do all that. Juuust barely. :)
I mean, it seems like we do that now anyway. I'm definitely okay with
you saying "yes, but the status quo is still kinda terrible." And I'm
okay with finding a bug and not being able to fix it in time for it to
be in the RC. What I don't want happening is for a bug to pop up just
before the meeting so that we end up spending half of of the go/no-go
meeting trying to reproduce the bug report.
I dunno, it's hard to be sure what number is right exactly.
Only because there's no right answer. :-) I'm fine with choosing 7
days as a starting point. If that's the only area of disagreement on
this proposal, then I'd say you've done pretty well.
He / Him / His
Fedora Program Manager