mwu committed https://github.com/mozilla-b2g/b2g-manifest/commit/619a55c60eb6b15ebce52afe08f889855036fc64 already. If you've got concerns about the workflow effect on devs, we should probably back it out in the short term.
Thanks for following up on this John. -Alex On Oct 9, 2012, at 1:44 PM, John Ford <[email protected]> wrote: > We already have a nightly branch of b2g-manifest. It's easy to switch from > mozilla-central to mozilla-aurora on both nightly and master. My only > concern is what happens to the local repositories that developers are using. > Switching repositories for gecko causes a lot of churn. Because the releng > maintained git mirrors use out of tree branching (i.e. separate repositories) > instead of an in-tree branch, we need to be careful about how we change the > manifests as there is a possibility that developer's local repositories are > messed up by this switch. > > I am testing this change and will reply to this thread when I have more > information on how we can make this change with minimal headache. When we > have a plan, I will make the changes to the manifests. > > John > > > On Oct 9, 2012, at 9:55 AM, Jonathan Griffin wrote: > >> Alex, >> >>> Jonathan will need to move Nightly/Stable builds over to mozilla-aurora >>> from mozilla-central for tonight's build, given the FF18 base. >>> >> >> The nightly builds utilize the build manifests at >> https://github.com/mozilla-b2g/b2g-manifest to select repos. I believe >> these likely need to change to point to the aurora branch. If we do that, >> then the builders will pick up this change automatically. mwu owns these. >> >> If there is some reason not to update those, then I can hack the builder to >> use aurora instead. >> >> Jonathan >> >> _______________________________________________ >> dev-b2g mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-b2g > _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
