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

Issue 623898 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

support for catapult release branches

Project Member Reported by achuith@chromium.org, Jun 28 2016

Issue description

We branch chromium and chromeos, but not catapult. 

There have often been cases where a catapult change breaks an important chromeos performance test, either for our partners or internal tools team, and we have no way of cherry-picking the catapult fix. The only recourse is to fast-forward all the changes up to TOT into the chromium branch.
 
Labels: Hotlist-CrOS-Catapult
Owner: kerz@chromium.org

Comment 3 by k...@google.com, Dec 16 2016

Status: WontFix (was: Untriaged)
You should be able to retroactively create a branch at the point that DEPS points at, then use that to cherry pick. You don't need branches created upfront.

Sign in to add a comment