1. Flame undergoes at the very least a smoke test for the nightly channel, there is no testing done on the nightly-latest. the nightly channel doesn't get updated until we have a green smoke test. See https://wiki.mozilla.org/B2G/QA/Flame_OTA for a history of versions
2. Yes, I am aware of Foxfooding Phase 2; we're trying to ramp up Aries to be ready for Foxfooding Phase 2. Having said that, we do need to have Flames up and running so that we can get contributors back on their feet again. Asa was planning to make a rally for getting Flame owners to contribute again and not having updates blocked him. To note, the current implementation of FOTA is a temporary fix, we need to migrate to Taskcluster since the pvtbuild server is going away. ie there may become yet another temporary break in service depending on the timing that pvtbuild server goes away. On Fri, Oct 23, 2015 at 9:33 AM, Brian King <[email protected]> wrote: > Hi Naoki, > > Thanks for the clarification. I guess I have no compelling reason to stop > the updates, but my concerns were two-fold: > > 1. Many Mozillians use the Flame as their primary device. Since 2.5 is not > fully-baked, it could bring instability into their day-to-day. > 2. Foxfooding Phase 2 is launching in ~10 days and this could have > coincided to amplify. > > Ruben and I are sending out a message to Mozillians in bit, if there is > anything we should flag in terms of features stability, let us know. > > > On 23 October 2015 at 18:04, Naoki Hirata <[email protected]> wrote: > >> Brian, short answer is no for the following reasons: >> 1) Reps and Mozillians aren't the only people using it. We have dev, QA, >> etc. using it and any feedback as soon as possible is necessary. We're >> trying to wrap up the project soon. Delaying any feedback for an >> announcement means getting less feedback for the project >> 2) I'm not sure what you mean by "put it on hold". >> 3) We fixed something that was broken previously because of not enough >> space on the device. ie switched over the OTA mechanism so that it works >> again. >> >> Unless you have a huge compelling reason, we're not going to stop the >> FOTA process. >> >> On Fri, Oct 23, 2015 at 7:52 AM, Brian King <[email protected]> wrote: >> >>> Hi, >>> >>> This is great, but I think we should should have coordinated better on >>> this. It would have been nice to send out a communication to Reps and >>> Mozillians and make sure we have something documented. Can we put this on >>> pause for a few days? >>> >>> On 22 October 2015 at 18:42, Asa Dotzler <[email protected]> wrote: >>> >>>> This is fantastic news. Thank you, Naoki and others for spending the >>>> time to get this working and keeping the Flame alive! >>>> >>>> - A >>>> >>>> On Thu, Oct 22, 2015 at 9:33 AM, Naoki Hirata <[email protected]> >>>> wrote: >>>> >>>>> We finished testing yesterday and Flames should now be FOTAing. >>>>> >>>>> There are two caveats: >>>>> 1) Make sure your date and time is set correctly on the phone >>>>> 2) Make sure you have the current base build for the flame. >>>>> >>>>> https://developer.mozilla.org/en-US/Firefox_OS/Phone_guide/Flame/Updating_your_Flame >>>>> >>>>> You should get an update, and should be able to update on those >>>>> conditions. >>>>> If you are stuck in the recovery mode, select reboot by navigating >>>>> using >>>>> the volume up/down and power to select >>>>> >>>>> Regards, >>>>> Naoki >>>>> >>>>> For those interested, these are the two bugs related to the FOTA >>>>> process: >>>>> 1215733 <https://bugzilla.mozilla.org/show_bug.cgi?id=1215733> - When >>>>> trying to FOTA the flame device, the device gives a "status text: Update >>>>> XML file malformed (200)" >>>>> <https://bugzilla.mozilla.org/show_bug.cgi?id=1215733> >>>>> 1214737 <https://bugzilla.mozilla.org/show_bug.cgi?id=1214737> - Device >>>>> should check to make sure that the proper fingerprint for a FOTA is being >>>>> used before trying to FOTA >>>>> <https://bugzilla.mozilla.org/show_bug.cgi?id=1214737> >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "b2g-internal" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To post to this group, send email to [email protected]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/a/mozilla.com/d/msgid/b2g-internal/CAJo_dWEpAKe_2xChyu1YNcQMogE1ewqdsnLk1h-cdbaOcn1TAg%40mail.gmail.com >>>>> <https://groups.google.com/a/mozilla.com/d/msgid/b2g-internal/CAJo_dWEpAKe_2xChyu1YNcQMogE1ewqdsnLk1h-cdbaOcn1TAg%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "b2g-internal" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To post to this group, send email to [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/a/mozilla.com/d/msgid/b2g-internal/CAKLrce%3DrihvWHFGJ%3DKDT0vH7DwgYaJZ5xXPrxC9hKWx2NG-sqw%40mail.gmail.com >>>> <https://groups.google.com/a/mozilla.com/d/msgid/b2g-internal/CAKLrce%3DrihvWHFGJ%3DKDT0vH7DwgYaJZ5xXPrxC9hKWx2NG-sqw%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> >>> >>> >>> -- >>> Brian King >>> @brianking | https://mozillians.org/u/kinger >>> Join Us | https://www.mozilla.org/contribute/ >>> >> >> > > > -- > Brian King > @brianking | https://mozillians.org/u/kinger > Join Us | https://www.mozilla.org/contribute/ >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
