Given that FxOS 2.6 is supposed to be a "quality release" and this change is most likely going to decrease quality, should we base 2.6 on Gecko 45 instead of Gecko 49 as it was initially planned?
Cheers, / Fernando El martes, 26 de enero de 2016, 19:06:46 (UTC+1), Naoki Hirata escribió: > To add what Andrew is stating: > > > > > On Tue, Jan 26, 2016 at 9:57 AM, Andrew Halberstadt <[email protected]> > wrote: > .. > > 1. Gecko based test harnesses (mochitest, xpcshell, reftest, etc) will > > eventually break and their corresponding jobs will be disabled. At some > > point, the test harness will need to undergo a large enough change that > > it will require a non-trivial amount of effort to not break B2G > > emulators and mulet. I'd estimate for most harnesses, this will happen > > sooner rather than later (within a quarter or two). When this happens, > > the jobs will be turned off completely so as not to waste money on our > > AWS bill. To be crystal clear, this means no more mochitest, reftest or > > xpcshell on B2G emulators. Mulet will likely last a little longer as it > > is similar enough to Firefox desktop. > > ... > > > If the gecko layer if it is not frozen and/or maintained: > 1) Anything on Firefox OS (ie TV) has a chance of breaking. > 2) Mulet might stay for a bit, but any contributor using Mulet will most > likely suffer breakage again. > 3) Any Dogfood or Nightly build that's made, ie Aries/Flame devices will end > up suffering breakage which may end up losing contributors for Firefox OS, > and possibly hurt gaining contributors for the project or any side project. > Basically, it kills all the efforts for foxfooding and dogfooding once again. > > > > 2. If at any point CD wishes to rejoin mainline development and run the > > set of Gecko unittests once again, re-integration will be a long and > > difficult process. > > > > 3. Gaia tests will still need a substantial effort to keep green. This > > one is more obvious, but still worth stating. It's really hard to keep a > > job green after the fact. In my experience, keeping jobs in Tier 3 for > > any extended period of time is not sustainable. CD will likely need to > > fork if they want to keep these jobs green. > > > > I think a question worth asking, is should we bother with Tier 3 at all? > > Or should we jump straight to disabling CD specific jobs. I guess it > > doesn't hurt to leave them running while they last, but in some cases > > this will be a very short time frame. > > > > In essence this will basically kill the Firefox OS train and possibly TV. If > we're going to kill Firefox OS, we should wrap up the TV work, and then have > everyone concentrate on these "approved side trains" that don't require > Firefox OS... _______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
