I use nightly-test. I receive 2 FOTAS a day without any issues at all.

Best regards,
Gabriela
QA Mozilla Hispano Team Responsible


http://www.mozilla-hispano.org
http://twitter.com/mozilla_hispano
http://facebook.com/mozillahispano




On 3 November 2015 at 07:24, Mihai Barbat <[email protected]> wrote:

> Hi
>
> To quote Naoki from an older email I got when I asked a similar question:
>
>
>
> *Nightly are QA qualified smoke test builds; this is a manual change over
> once the smoke tests are run and things pass.*
>
> *Nightly-test are the staging for QA to smoke test the builds, or further;
> I would not recommend using this channel at all.  This changes when QA
> needs a build to test, or use for testing FOTA or other things.*
>
> *Nightly-latest is an unqualified build that happens on a daily basis.*
>
> For the Flame phone, you can check them here:
> https://wiki.mozilla.org/B2G/QA/Flame_OTA
>
> On Tue, Nov 3, 2015 at 11:17 AM, Dietrich Ayala <[email protected]>
> wrote:
>
>> I've been pretty confused about the update channels for a while: Which
>> releases are on which channels for which devices at what frequency? I have
>> no idea :)
>>
>> And now I've learned that "nightly" is not actually "nightly" anymore...
>>
>> Now that we're pushing on improving participation, making update channels
>> clear is more important than ever.
>>
>> I've started a list here, and there are a bunch of questions. If you know
>> any of this information, please add it :)
>>
>> https://public.etherpad-mozilla.org/p/fxos-update-channels
>>
>> Once the information is settled, we can move it over to MDN.
>>
>>
>> _______________________________________________
>> dev-fxos mailing list
>> [email protected]
>> https://lists.mozilla.org/listinfo/dev-fxos
>>
>>
>
> _______________________________________________
> dev-fxos mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/dev-fxos
>
>
_______________________________________________
dev-fxos mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-fxos

Reply via email to