Determine why crbug/815161 wasn’t marked as a release blocker until after stable release |
||
Issue descriptionWriting a postmortem for crbug/815161, I noticed that this bug was filed by hand and didn't have RBS applied until much later, after stable had already gone out. It's not clear to me what should be different, but here are a couple of ideas: - Should crash bugs automatically block stable unless a No-Release-Block-Stabls label is applied? - Should this bug have been filed automatically (issue 838617)?
,
May 1 2018
AFAIK clusterfuzz reports crashes automatically. Other crashes are triaged and reported by test team. + abdulsyed@ (Desktop Release TPM) & bustamante@ (Test Lead), to take their input as well.
,
May 21 2018
Bulk edit** This bug has the label Postmortem-Followup but has not been updated in 3+ weeks. We are working on a new workflow to improve postmortem followthrough. Postmortems and postmortem bugs are very important in making sure we don't repeat prior mistakes and for making Chrome better for all. We will be taking a closer look at these bugs in the coming weeks. Please take some time to work on this, reassign, or close if the issue has been fixed. Thank you. |
||
►
Sign in to add a comment |
||
Comment 1 by sdy@chromium.org
, May 1 2018Status: Assigned (was: Untriaged)