75
edits
Firefox OS/Flame: Difference between revisions
m
→Getting a Flame: fixed mangled link to Foxtrot
m (→Getting a Flame: fixed mangled link to Foxtrot) |
|||
| Line 26: | Line 26: | ||
'''Foxtrot.''' We have about 200 devices available for members of our community (volunteers and employees) who are not part of the core OS dev teams, who will use the phones regularly, and who will participate in product surveys, focused testing efforts, and be available to help us gauge the quality of specific features and the overall product. | '''Foxtrot.''' We have about 200 devices available for members of our community (volunteers and employees) who are not part of the core OS dev teams, who will use the phones regularly, and who will participate in product surveys, focused testing efforts, and be available to help us gauge the quality of specific features and the overall product. | ||
To apply to the program, head over to our [http://www.surveygizmo.com/s3/1709863/Foxtrot-Application | To apply to the program, head over to our [http://www.surveygizmo.com/s3/1709863/Foxtrot-Application Foxtrot Application]. | ||
Note that the Foxtrot program will have its software release channel, based on "verified" nightly builds that will be updated about once a month. It will require an initial flash like the nightly channel (see MDN article). We don't have our solution for nightly builds yet but when we do, and when we've evaluated all of the applications, we'll start sending out Flames. | Note that the Foxtrot program will have its software release channel, based on "verified" nightly builds that will be updated about once a month. It will require an initial flash like the nightly channel (see MDN article). We don't have our solution for nightly builds yet but when we do, and when we've evaluated all of the applications, we'll start sending out Flames. | ||