+ the right Wesly
hi All,
V184 has been received and under testing, please see my comments inline.
Wesly will share our v184 once test is done, target to share it by today
10/2
thank you very much
Francis Lee
Technical Account Manager, Mozilla Taiwan
Tel: +886-2-87861100 #337
[email protected]
On 2014-09-30 2:24 AM, Tony Chung wrote:
Sebastian is correct, v180 is originally intended for the development
crowd to use. Notice its also rooted, with whatever configurations
are set by default.
Francis and Wesley from the TAMs team will communicate the wish list
of what should be fixed in the next version of the flame base image.
So far, these are the requests that i’m hearing:
* include flash.bat for windows users
fixed in v184
* emergency rescure tool in MDN not work, either tool issue or
Teleweb.ini config. URL problem
Wesly is following up with T2M for solution
* remove engineering apps from the default homescreen
* No fonts when we had previous base images which had fonts bundled.
fixed in v184
Please speak up now before the changes are made before the next image.
How did this happen in the first place and how can we make sure
it doesn't happen again? Does QA do a quality sign-off on these
images?
Kevin, yes, QA does do a quality check of each Flame base image out of
box. if anyone (Mozilla internal only) is interested, you can find
the test plan and results here: http://goo.gl/8iEzwr
Thanks,
Tony
On Sep 29, 2014, at 11:01 AM, Sebastián Enrique Becerra Cancino
<[email protected] <mailto:[email protected]>> wrote:
But Kevin, Flame devices are not intended for end users, actually as
a base image should have the engineer apps and then update to 2.0
with non-engineer apps.
--
Atte.
Sebastián Enrique Becerra Cancino
Facebook: SebaEBC
Twitter: @SebaEBC
Tel.: +56 9 9169 0521
On Mon, Sep 29, 2014 at 2:58 PM, Kevin Grandon <[email protected]
<mailto:[email protected]>> wrote:
The main issues I have noticed with the v180 base image are
pretty bad.
1 - No fonts when we had previous base images which had fonts
bundled.
2 - Engineering apps are installed by default - this is not ideal
for end users because a lot of them can not be removed.
I think that these are P1 issues, and the v180 image is not ready
for release. Can we take the v180 base image down until we have
something half way decent to offer users?
How did this happen in the first place and how can we make sure
it doesn't happen again? Does QA do a quality sign-off on these
images?
Best,
Kevin
----- Original Message -----
From: "Asa Dotzler" <[email protected] <mailto:[email protected]>>
To: [email protected]
<mailto:[email protected]>
Sent: Wednesday, September 24, 2014 4:37:23 PM
Subject: [b2g] Please update your Flame to the new base image
The Flame reference phone, which many of you all are using for
development, testing, and dogfooding, is transitioning from a
Gonk that
is based on Android 4.2 JellyBean to one based on 4.4 KitKat.
Many of you will likely have flashed the v123 base image (Firefox OS
1.3) and then done a "shallow" flash of contemporary Gecko and
Gaia on
top of that. Having done that, you are probably receiving nightly
updates of the Gecko and Gia layers from Mozilla.
Those updates are going to stop real soon now because we're
moving our
development and testing focus to the KitKat-based Gonk and trying to
avoid a long and painful overlap period.
Unfortunately, we don't have a simple mechanism for updating you
to the
new builds so you are going to have to repeat those steps of
flashing a
new base image and then shallow flashing Gecko and Gia to
continue to
receive nightly updates.
The new base image is v180 and the new Gecko and Gaia bits live in
directories on FTP appended with -KK.
Tony has updated the QA docs and I've updated the Flame page at
MDN* to
point to the new v180 base image and the new Mozilla FTP
directories.
We're in a period of transition that becomes more expensive the
longer
we're in it, so please take a moment today or tomorrow to move to
the
new image and updates. The last thing we all need is for QA and
Engineering to spend more time chasing down phantom bugs that
cannot be
reproduced on the latest bits.
I recognize that this is not an ideal workflow and we are
investigating
ways to mitigate these kinds of stop and reset requirements. It's a
challenge dealing with a system that includes bits Mozilla cannot
host
and distribute so we appreciate your patience as we go through
the first
of these transitions, learn from it, and make improvements for
next time.
- A
*
https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame#Updating_your_Flame%27s_software
_______________________________________________
dev-b2g mailing list
[email protected] <mailto:[email protected]>
https://lists.mozilla.org/listinfo/dev-b2g
_______________________________________________
dev-b2g mailing list
[email protected] <mailto:[email protected]>
https://lists.mozilla.org/listinfo/dev-b2g
_______________________________________________
dev-b2g mailing list
[email protected] <mailto:[email protected]>
https://lists.mozilla.org/listinfo/dev-b2g
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
