> Also, I think the "can be accepted" should be "must be accepted". Except the obvious case where it doesn't make sense, like the wallpapers bug. I think we don't need to codify that corner case.
>
I'm okay with this. In the case of the wallpapres bug, we'd either
ship it later (so it wouldn't come up for F N+1 Beta) or close it as
invalid. I agree that it's a corner case not worth legislating.

So while the immediate paragraph says "can", the ending paragraph is much more clear that it's supposed to happen almost always (the wallpaper issue is a nice example of 'almost'). Also, the "can" sentence speaks only about the very next milestone, while the ending paragraph speaks about all the options. So I wonder whether we need adjustments at all. Or perhaps just completely remove "In these circumstances, the bug can instead be accepted as a blocker for the next milestone release." sentence to avoid confusion/collision with the last paragraph.