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

Issue 733342 link

Starred by 2 users
Status: Untriaged
Owner: ----
Cc:
marq@chromium.org
█ cma...@chromium.org
eugene...@chromium.org
█ noyau@chromium.org
pinkerton@chromium.org
linds...@chromium.org
pkl@chromium.org
rohitrao@chromium.org
kkhorimoto@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Task



Sign in to add a comment

Improve process for branching during large refactors

Project Member Reported by kkhorimoto@chromium.org, Jun 14 2017 
The M58 performance issue (go/chromepostmortem451) was the result of branching at a non-performant commit during a large scale refactor.  As a follow-up action item for this issue, we should develop a process for branching during a large refactor to ensure that we don't ship a bad intermediary state.
Project Member

Comment 1 by sheriffbot@chromium.org, Jun 15 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 2 by pkl@chromium.org, Jun 26 2018

Cc: eugene...@chromium.org
marq, rohitrao, eugenebut: any process improvements possible? Should refactors be required to be behind a flag as well?

Comment 3 by eugene...@chromium.org, Jun 26 2018

Labels: -Type-Bug Type-Task
I think all new large refactorings were landed behind the flags and the old code was cleaned up after stabilization. Do we consider this as an improvement?
►

Sign in to add a comment