Hello mobile-firefox-dev, On Wed, Mar 16, 2016 at 1:24 PM, Nicholas Alexander <nalexan...@mozilla.com> wrote:
> Hi folks, > <snip> > Tentative plan > ============== > > I would like to try a "controlled burn": I would like to work with QA > to produce a targeted upgrade/downgrade manual test sign-off process, > and then try to build Nightly with Gradle for a day (or several), then > revert to |moz.build|. > > Our testing population is small, but this should reveal catastrophic > failures. > > The next uplift is in slightly over a month (2016-04-18, see [4]), so > I'd like to try to do this test during March. If there are schedule > considerations, please raise them here. > An update on this: as most of y'all know, I have transitioned to working 100% on Project Tofino [1]. That's pushed this to the back-burner. I think the things that remain to be done are: * set up Task Cluster jobs for building --with-gradle and without gradle. We need these so that we don't regress moz.build vis-a-vis Gradle and vice versa, without regard to which is the main buildbot job actually producing Nightly builds. This is just copy-paste-rename from the existing jobs and tweaking mozconfigs. * test that single locale l10n repacks work locally as much as possible (this is delicate and hard to get right in automation). I think there's support for testing in automation now; Nicholas Thomas knows what's happening here. * manually test upgrades across the different build configurations. * flip the switch and watch for fallout! I'm sorry to have left this project hanging. Yours, Nick [1] http://mozilla.github.io/tofino/
_______________________________________________ mobile-firefox-dev mailing list mobile-firefox-dev@mozilla.org https://mail.mozilla.org/listinfo/mobile-firefox-dev
