I think that would essentially make the blocker review the go/no-go meeting. If the RC has to appear by the end of the meeting, there’s no time to allow pending updates for newly-accepted blockers, etc. I think it takes ~5 hours for a compose these days, so to have an RC by the scheduled end of the meeting would require starting it 2 hours before the meeting begins.
On the other hand, we could require the RC request to go in some small number of hours after the meeting. This would allow for pending blocker fixes and FEs to go into the RC, and given the general reliability of composes, these days, I’m not too concerned about it taking 2 days to actually get the compose.
The other issue is that there’s no particular reason that Blocker Review meeting needs to be on Mondays. If that meeting ever needs to move for some reason, I don’t know if I want the RC request to still be tied to it. For example, what happens if QA decides the Blocker Review meeting should be on Fridays instead?
Of course, there’s not a particular reason we need to have the Go/No-Go meeting on Thursdays, except that it’s apparently the latest we can decide and still have the release ready on Tuesday. But there’s no particular reason we need to release on Tuesdays except that we always have…