On Fri, Nov 30, 2012 at 3:07 PM, Alex Keybl <[email protected]> wrote: > There will be a fourth upcoming (12/11 or sooner) when we switch from using > Gecko on mozilla-beta to mozilla-b2g18. If you have good ideas on how to > prevent developer pain around the transition, please follow up with John/Hal > separately. Thanks Hub!
That switch should be completely seamless; mozilla-b2g18 should live in the same repository and have the same hashes as the latest mozilla-beta, so devs won't have to take any particular action other than using a different upstream branch for new patches. > On Nov 29, 2012, at 6:52 AM, Hubert Figuière <[email protected]> wrote: > >> On 28/11/12 04:35 PM, John Ford wrote: >>> Please note that this repository has a different set of commit hashes than >>> other repositories we've used for gecko. It would be prudent to make >>> backups of your local copy of gecko before syncing to the manifests >>> tomorrow. >>>> >>>> If you have any questions or if there are any critical concerns, please >>>> let me know as soon as possible. >> >> May I raise the voice on how disruptive this kind of unnecessary changes >> make it on developers, and how |repo sync| fail to even deal with it >> properly, giving another reason to not do that. >> >> Non-withstanding that any of us with patches are going through a bucket >> of pain to rebase things... I know we should already be used to it as it >> is already the THIRD repository. >> >> Hub >> _______________________________________________ >> 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 _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
