>From my perspective, the best way is to start building from b2g32_v2_0, which now has the code that was on Aurora on Monday. http://hg.mozilla.org/releases/mozilla-b2g32_v2_0 https://github.com/mozilla/gecko-dev/tree/b2g32_v2_0
On 7/22/14 7:00 AM, Ben Kelly wrote: > It seems after the merge my aurora OTA updates stopped getting recognized. I > assume because the %VERSION% part of the URL is no longer matching. > > Whats the best way to get past the branch on OTA updates? Changing the > update URL in the developer menu does not work (bug 1035807). > > Thanks! > > Ben > > ----- Original Message ----- > From: "Aki Sasaki" <[email protected]> > To: "dev-b2g" <[email protected]> > Sent: Monday, July 21, 2014 9:19:18 PM > Subject: [b2g] mozilla-b2g32_v2_0 branch now live > > As of today's uplift, the Gecko side of B2G v2.0 now lives on the > mozilla-b2g32_v2_0 branch, *NOT* mozilla-aurora. Patches that are > blocking-b2g:2.0+ should be landed there now. For more information, see > the page below which always contains the latest information. > https://wiki.mozilla.org/Release_Management/B2G_Landing#v2.0.0 > > As a reminder, B2G v2.1 development remains on mozilla-central through > the duration of the Gecko 34 development cycle due to end on Sept 1, so > there is no change for where v2.1 patches are to land. > _______________________________________________ > 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
