Tl;dr: v2.0 3rd party repo revisions have been locked down to specific changesets. This should reduce unexpected churn, but will require us to explicitly bump these revisions if we want to pick up a change in v2.0. We will also lock down v1.4, v1.3t, and v1.3 shortly.
I locked down the third party repo revisions here: https://github.com/mozilla-b2g/b2g-manifest/commit/cdefade4ea94832a1f98edf0dc3f9c25f2f9bcc5 For the most part, we're operating on either a v2.0 branch or a specific changeset. We also have non-v2.0 branch names for certain mozilla-forked repos because: * several repos were in use with multiple branches, e.g. jellybean and kitkat branches * I had to choose a single branch point, so I chose the most common. right now that's jb. * I had to choose whether to lock down the non-v2.0 revisions, and I chose not to at this point. If it's better to lock these down, that's not difficult to fix. The best news: even though the diff above is large, b2g_bumper (our script that points the remotes at git.m.o and pins each repo to a revision, for more deterministic releng builds) then converted the v2.0 manifests and found no 3rd party changes, only gaia v2.0: https://hg.mozilla.org/releases/mozilla-aurora/rev/9c915d7c224d This means the diff worked properly for all devices that releng builds. I will be proceeding quickly onto v1.4, so this is done before any potential 1.4d branch. This is the same script we'll be using going forward the next merge day; I believe we'll create v2.1 branches on September 1. The script is tracked in https://bugzilla.mozilla.org/show_bug.cgi?id=918055 . Locking down 3rd party repo revisions is tracked in https://bugzilla.mozilla.org/show_bug.cgi?id=910745 . _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
