More thorough explanation of my concerns...  I agree with punting bugs that were filed before a milestone branched, to the next milestone, if they don't meet certain criteria.  However, any bug filed against a milestone post branch indicates a branch regression, which we should try to follow up on.  Punting it might cause us to miss it.

Will take a closer look later today. I do agree that punting immediately in cases where the bug was filed after the branch doesn't make sense.

We just punted a top crash bug for M53 hours after it was filed - https://bugs.chromium.org/p/chromium/issues/detail?id=634828#c1 - should we turn the punting off until we can address this?  Or will we have the fix soon?

Sorry about that, bumping the priority on this. It probably isn't a difficult fix, but I haven't had a chance to look yet. I'll disable the rule until I do.

Bulk edit: archiving a few bugs assigned to me that no longer seem relevant. Please reopen if this is still something you'd like to see fixed and I'll re-evaluate it.