New issue
Advanced search Search tips

Issue 773935 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocked on:
issue 825063
issue 888082

Blocking:
issue 663061
issue 456273
issue 536095
issue 773936



Sign in to add a comment

Release branches should reflect "reality" and use pinned sub-repos

Project Member Reported by dpranke@chromium.org, Oct 12 2017

Issue description

Currently, when we branch Chromium for a release, we allow a few sub-repos to "float" at unpinned versions of branches in their repos (e.g., v8, or skia), in order to make it easier to get changes in the subrepos.

This is actually bad, because it means that the branch builds are not well-controlled, and don't actually reflect what the actual releases are.

It would be better if every sub-repo was pinned, and we had auto-rollers, so that if a v8 dev checks in a change on the v8 release branch, we'd auto-update the v8 revision in src/DEPS on the matching branch. Then things would be pinned just like they are on trunk, and would also be more likely to match the actual release buildspecs.
 
Blocking: 773936

Comment 2 by mmoss@chromium.org, Jan 18 2018

Blocking: 663061

Comment 3 by mmoss@chromium.org, Jan 18 2018

Blocking: 456273

Comment 4 by mmoss@chromium.org, Jan 18 2018

Cc: -phajdan.jr@chromium.org
Owner: mmoss@chromium.org
Status: Assigned (was: Available)
My plan to revamp buildspecs (http://doc/1j6WlkSgqTNsrmEwilRi82Rb6Km4d6EQvVAP_wPLZU9U) includes migrating source-of-truth to the public DEPS, and pinning the currently floating repos with auto-rollers, so assigning to me.

Comment 5 by mmoss@chromium.org, Mar 23 2018

Blockedon: 825063
Cc: -amineer@chromium.org
No longer on the Chrome team, e-mail me @google.com if any attention still required from me here, otherwise good luck!
Blocking: 536095
Blockedon: 888082

Sign in to add a comment