Lines Matching +full:- +full:- +full:branch

1 # Choosing an ANGLE branch for your project
6 This document illustrates how to choose a branch of ANGLE which can be expected
13 matching Chromium branch. These branches will be created from the revision which
14 that Chromium branch points to as its dependency. So, for example, the
15 `chromium/2013` branch point is at r28bcf4ff, because [Chromium's dependency
16 file for the 2013 branch]
21 works to choose an appropriate ANGLE branch for your project. You will, however,
22 likely want to make sure that you choose a branch that is used for a relatively
26 branches will be short-lived.
28 **We recommend choosing a branch corresponding to a Beta or Stable Chromium
31 ## Matching a Chromium release to an ANGLE branch
37 note the branch listed in the `true_branch` column. This identifies the ANGLE
38 branch used by that Chromium release.
43 branch has been created, and that branch is used by a Chromium release, the
45 Chromium and any other projects using that branch. You should need only to
48 ## Cherry-picking a change to a release branch
51 release branch. To do this, first look up the branch number in
53 corresponds to branch number 2883.
57 `chromium/[branch_number]` as the branch to merge to.
62 2. `git cherry-pick [commit_hash]`
66 Have the cherry-pick reviewed, and then land it. It's also OK to skip
71 Stable branch. A Skia auto-roller updates the DEPS file in the corresponding
72 Chromium branch automatically once the ANGLE change is merged into an ANGLE
73 branch. To make sure that your change has made it into Chromium you can check
74 these auto-rollers:
76 1. https://autoroll.skia.org/r/angle-chromium-beta-autoroll
77 1. https://autoroll.skia.org/r/angle-chromium-stable-autoroll