Bug 1604873 Comment 3 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Who said that an unfixed P1 automatically becomes a blocker? Sure, if you notice a regression one day before the release, you wouldn't block on it. Also see: https://firefox-bug-handling.mozilla.org/triage-bugzilla. IMHO, any visible regression should be a P1, whether to manage to fix it in the current cycle is another story. You really want to get this fixed in TB 78 when you'll have many other things to worry about? Or shouldn't it be fixed rather sooner than later, and if due to the holidays it doesn't happen in 72, it should happen in 73?

BTW, we're not blocking on these 17 P1 bugs either. You might want to review the priorities on them.
Who said that an unfixed P1 automatically becomes a blocker? Sure, if you notice a regression one day before the release, you wouldn't block on it. Also see: https://firefox-bug-handling.mozilla.org/triage-bugzilla. IMHO, any visible regression should be a P1, whether to manage to fix it in the current cycle is another story. You really want to get this fixed in TB 78 when you'll have many other things to worry about? Or shouldn't it be fixed rather sooner than later, and if due to the holidays it doesn't happen in 72, it should happen in 73?

BTW, we're not blocking on these 17 P1 bugs either. You might want to review the priorities on them.

EDIT: Oops, forgot to paste the link: https://mzl.la/2PVqRPa

Back to Bug 1604873 Comment 3