hi Nicholas, Archaeopteryx; Unagi builds are being deprecated because we need to update to ICS strawberry update, for better interaction with WebGL. Depending on what your usage case is, and what branch you are working on, there are different devices available. And dont forget, there are also b2g-desktop and simulator builds available. For more details, see Faramarz's post to dev-b2g earlier today.
Turning off unagi builds in automation is what we're talking about here. If history is any indicator, this means that soon afterwards the code to generate unagi builds will start to bitrot, as changes for new devices land. Hope that clarifies. John. ==== On Wed Aug 28 00:48:44 2013, Archaeopteryx wrote: > The Unagi is the phone provided by the Mozilla l10n team to Gaia > localizers. So if Unagi gets EOL-ed, these people would all need new > phones for localization, preferred a phone with nightly updates. The > Unagi would need replacement when Gaia 1.2 localization starts (or > with a short delay). > > CC-ing l10n team on this. > > Archaeopteryx > > -------- Original-Nachricht -------- > Betreff: unagi update EOL > Von: Aki Sasaki <a...@mozilla.com> > Datum: 2013-08-28 3:38 >> At today's cross-functional B2G meeting, I asked whether it made sense >> to point the old unagi update channels at the new ones, so older builds >> would get updated to the latest: >> https://bugzilla.mozilla.org/show_bug.cgi?id=909311 >> >> However, it turns out that we're phasing out unagi as a testing >> platform. Would it make sense to turn off unagi updates (and >> potentially releng-supported unagi builds, as well)? >> > > _______________________________________________ > dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g _______________________________________________ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
