New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 683751 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Apr 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Determine process for triaging and tagging release blocking issues

Project Member Reported by amineer@chromium.org, Jan 22 2017

Issue description

Follow-up from postmortem: https://docs.google.com/a/google.com/document/d/1aM0Kr_vYhu2yWb0BFQRjWrJQnKWXRoINlnSx6PcGPCM/edit?usp=sharing

 Issue 670837  was identified as a release blocker, but was not tagged with OS-Android.  This led to the Chrome for Android team shipping a version to stable with the bug present.  This caused us to halt the rollout and respin, which costs the release team time and users money (via bandwidth).  We should implement a process to explicitly review all release blocking bugs to cross-verify platform applicability so that this does not occur again.
 
Cc: pbomm...@chromium.org
Status: Fixed (was: Assigned)
I have updated the team to tag Android and ChromeOS automatically if a we can reproduce the issue and falls under Blink and V8 components. Going forward we would be tagging them accordingly.

Since this been already taken care of I am marking the bug as Fixed

Sign in to add a comment