First 11.09 Linaro Android Candidate Builds are done for (Linux 3.0.3, GCC 4.6, libjpegturbo) Panda, Beagle, Beagle xM, iMX53, Origen, Snowball
Linaro has been hard at work getting the first 11.09 candidate builds out. All instructions, test results and tips are listed at each link.
Of note:
Replaced jpeg lib with libjpeg-turbo Linux version 3.0.3 gcc version 4.6.2 20110813 (prerelease) Compiled with -O3
Panda https://android-build.linaro.org/builds/~linaro-android/panda-11.09-release/...
Stage Panda https://android-build.linaro.org/builds/~linaro-android/stage-panda-11.09-re...
Beagle, Beagle xM https://android-build.linaro.org/builds/~linaro-android/beagle-11.09-release...
Stage iMX53 https://android-build.linaro.org/builds/~linaro-android/stage-imx53-11.09-re...
Stage Origen https://android-build.linaro.org/builds/~linaro-android/stage-origen-11.09-r...
Snowball https://android-build.linaro.org/builds/~linaro-android/stage-snowball-11.09...
The term "Stage" is used to indicate builds that contain patches that haven't been upstreamed.
The only build with graphics acceleration is Stage Panda.
Enjoy the builds. As always, please file lots of bugs (https://bugs.launchpad.net/linaro-android/+filebug)%21
(Google Plus: https://plus.google.com/104422661029399872488/posts/Yvg3iv34E9s)
-Zach
On Fri, Sep 09, 2011 at 12:09:55PM -0500, Zach Pfeffer wrote:
The term "Stage" is used to indicate builds that contain patches that haven't been upstreamed.
That a pretty confusing term. Are we sure we want to call it that?
On Fri, Sep 9, 2011 at 7:34 PM, Christian Robottom Reis kiko@linaro.orgwrote:
On Fri, Sep 09, 2011 at 12:09:55PM -0500, Zach Pfeffer wrote:
The term "Stage" is used to indicate builds that contain patches that haven't been upstreamed.
That a pretty confusing term. Are we sure we want to call it that?
This comes out of me complaining to android team that they titled everything that didn't use mainline kernel as "LEB", no matter how well that worked, no matter what level of hardware enablement those builds came with, no matter if those builds are booting to UI or not.
To avoid that we said that the technical/functional build name shouldn't include the term leb at all, but rather mark those builds as non-mainline in a different way. The term LEB would then become a badge (think about certification) that gets awarded by release team for builds _after_ they have gone through validation/testing and have been officially confirmed to meet LEB requirements.
That said, I don't like the name "Stage" much either. Idea: How about we mark the ones that are not "stage" as "mainline" and drop the "stage" marker from the other build names?
On 12 September 2011 06:00, Alexander Sack asac@linaro.org wrote:
On Fri, Sep 9, 2011 at 7:34 PM, Christian Robottom Reis kiko@linaro.org wrote:
On Fri, Sep 09, 2011 at 12:09:55PM -0500, Zach Pfeffer wrote:
The term "Stage" is used to indicate builds that contain patches that haven't been upstreamed.
That a pretty confusing term. Are we sure we want to call it that?
This comes out of me complaining to android team that they titled everything that didn't use mainline kernel as "LEB", no matter how well that worked, no matter what level of hardware enablement those builds came with, no matter if those builds are booting to UI or not.
To avoid that we said that the technical/functional build name shouldn't include the term leb at all, but rather mark those builds as non-mainline in a different way. The term LEB would then become a badge (think about certification) that gets awarded by release team for builds _after_ they have gone through validation/testing and have been officially confirmed to meet LEB requirements.
That said, I don't like the name "Stage" much either. Idea: How about we mark the ones that are not "stage" as "mainline" and drop the "stage" marker from the other build names?
I think stage is okay. Its short for staging which is used in the kernel as a place for things which aren't mainline.
If I hear of any other issues with the name I'll think we can reevaluate it, but overall I think the term stage is okay. Plus, we should call out the builds that aren't mainline, since they should be the exception and not the rule.
--
- Alexander
Linaro.org | Open source software for ARM SoCs http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
On Mon, Sep 12, 2011, Zach Pfeffer wrote:
I think stage is okay. Its short for staging which is used in the kernel as a place for things which aren't mainline. If I hear of any other issues with the name I'll think we can reevaluate it, but overall I think the term stage is okay.
Sorry for the bikeshedding. "staging" or "staged" would in my eyes be much clearer than "stage".
On 12 September 2011 06:36, Loïc Minier loic.minier@linaro.org wrote:
On Mon, Sep 12, 2011, Zach Pfeffer wrote:
I think stage is okay. Its short for staging which is used in the kernel as a place for things which aren't mainline. If I hear of any other issues with the name I'll think we can reevaluate it, but overall I think the term stage is okay.
Sorry for the bikeshedding. "staging" or "staged" would in my eyes be much clearer than "stage".
How about staging?
To keep the build linage I'll keep the current names for the 11.09 release.
-- Loďc Minier
On Mon, Sep 12, 2011 at 11:36 PM, Loïc Minier loic.minier@linaro.org wrote:
On Mon, Sep 12, 2011, Zach Pfeffer wrote:
I think stage is okay. Its short for staging which is used in the kernel as a place for things which aren't mainline. If I hear of any other issues with the name I'll think we can reevaluate it, but overall I think the term stage is okay.
Sorry for the bikeshedding. "staging" or "staged" would in my eyes be much clearer than "stage".
Agreed. Use English, which also means no abbreviations.
Releases should have the shortest name. Development versions should have a unique suffix. And the shed should be a pinker shade of green.
-- Michael
On 12 September 2011 16:36, Michael Hope michael.hope@linaro.org wrote:
On Mon, Sep 12, 2011 at 11:36 PM, Loïc Minier loic.minier@linaro.org wrote:
On Mon, Sep 12, 2011, Zach Pfeffer wrote:
I think stage is okay. Its short for staging which is used in the kernel as a place for things which aren't mainline. If I hear of any other issues with the name I'll think we can reevaluate it, but overall I think the term stage is okay.
Sorry for the bikeshedding. "staging" or "staged" would in my eyes be much clearer than "stage".
Agreed. Use English, which also means no abbreviations.
Releases should have the shortest name. Development versions should have a unique suffix. And the shed should be a pinker shade of green.
So:
stage-origen-11.09-release stage-panda-11.09-release stage-snowball-11.09-release stage-imx53-11.09-release panda-11.09-release beagle-11.09-release
Would be:
origen-staging-11.09-taupe panda-staging-11.09-mauve snowball-staging-11-burntsienna imx53-staging-11.09-orangecrush panda-11.09-crucialpink beagle-11.09-black
minus the colors ;)
On Mon, Sep 12, 2011 at 10:12:22PM -0500, Zach Pfeffer wrote:
stage-origen-11.09-release stage-panda-11.09-release stage-snowball-11.09-release stage-imx53-11.09-release panda-11.09-release beagle-11.09-release
Would be:
origen-staging-11.09-taupe panda-staging-11.09-mauve snowball-staging-11-burntsienna imx53-staging-11.09-orangecrush panda-11.09-crucialpink beagle-11.09-black
The main problem I see with staging is that it's simply not true in the common sense of the word staging -- it implies that what is in staging today is intended to become upstream (or "mainstream") in the future, whereas there's lots that is in the LT branches which, well, isn't.
OTOH, I really can't come up with good alternatives to 'staging' that I don't see other problems with. There was a "non-upstreamable" suggestion a while back, and I have been known to call them "dirty" ;-)
On Tue, 13 Sep 2011 15:16:00 -0300, Christian Robottom Reis kiko@linaro.org wrote:
The main problem I see with staging is that it's simply not true in the common sense of the word staging -- it implies that what is in staging today is intended to become upstream (or "mainstream") in the future, whereas there's lots that is in the LT branches which, well, isn't.
OTOH, I really can't come up with good alternatives to 'staging' that I don't see other problems with. There was a "non-upstreamable" suggestion a while back, and I have been known to call them "dirty" ;-)
What about taking a cue from gstreamer?
good, bad and ugly
I don't think we have the same division of them, but "ugly" could work, in a similar spirit to "dirty," but without some of the implications?
Thanks,
James
On Tue, Sep 13, 2011, James Westby wrote:
What about taking a cue from gstreamer? good, bad and ugly I don't think we have the same division of them, but "ugly" could work, in a similar spirit to "dirty," but without some of the implications?
[ The names of course come from the movie, but sometimes GStreamer folks regretted picking these names because end-users didn't really understand why they should run something "bad" or even "ugly". ]
On 13 September 2011 15:21, Loïc Minier loic.minier@linaro.org wrote:
On Tue, Sep 13, 2011, James Westby wrote:
What about taking a cue from gstreamer? good, bad and ugly I don't think we have the same division of them, but "ugly" could work, in a similar spirit to "dirty," but without some of the implications?
[ The names of course come from the movie, but sometimes GStreamer folks regretted picking these names because end-users didn't really understand why they should run something "bad" or even "ugly". ]
I agree. I really don't like to use the terms bad or ugly to describe work. I think it sets the wrong tone.
It sounds like staging is generally okay with people. I tend to take the view that its always possible to upstream the outstanding patches, though it may not be likely - the glass is half full, right?
-- Loďc Minier
-
Alexander Sack -
Christian Robottom Reis -
James Westby -
Loïc Minier -
Michael Hope -
Zach Pfeffer