+1 bundling with test apps is annoying and reminded me to file https://bugzilla.mozilla.org/show_bug.cgi?id=1031961 a while ago, anyone wanna give me a pointer and hopefully I can get round to fixing it, its mostly the test apps, but seeing as they are reference devices that dont go through certification, I dont see any reason to not let users delete stuff they dont want
On 29 September 2014 20:18, Kevin Grandon <[email protected]> wrote: > Most of these testing apps are not even needed for developers besides when > we are developing the feature. We should probably do a better job of > removing old testing apps, or opting into installing them. > > They should not be on the base image though as they are not useful for > development in most cases, and generally hamper the dogfooding experience. > Also if these are on the base image, then it's likely that we did not > bundle with an optimized profile, so performance is probably worse as well. > > Best, > Kevin > > ----- Original Message ----- > From: "Sebastián Enrique Becerra Cancino" <[email protected]> > To: "Kevin Grandon" <[email protected]> > Cc: "Asa Dotzler" <[email protected]>, [email protected] > Sent: Monday, September 29, 2014 11:01:28 AM > Subject: Re: [b2g] Please update your Flame to the new base image > > 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]> > 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]> > > To: [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] > > https://lists.mozilla.org/listinfo/dev-b2g > > _______________________________________________ > > dev-b2g mailing list > > [email protected] > > https://lists.mozilla.org/listinfo/dev-b2g > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g >
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
