Those are fine names. I have no objections.
The full names are kind of cumbersome to use in everyday speech so I predict nicknames :)
And I think we need a frequently linked-to wiki page explaining the whole idea and also presenting rationales for each one of them.
The flop side of such an improvement is to decide which wiki pages need to be updated and which are better left alone. I see work coming my way.
/Tony
On 30 January 2012 21:39, Zach Pfeffer zach.pfeffer@linaro.org wrote:
Aye. :) Good catch.
On 30 January 2012 14:37, Mathieu Poirier mathieu.poirier@linaro.org wrote:
I'm all for it as long as snowball gets named 'ics-igloo-stable-gcc46-snwoball' rather than 'ics-igloo-stable-gcc46-panda'.
Mathieu.
On 12-01-30 12:24 PM, Zach Pfeffer wrote:
So our current naming scheme is awful.
staging- landing- tracking-
ick ick ick
We'd like to make this better, here's the idea:
old new
staging-vexpress-a9 ics-armlt-stable-gcc46-vexpress-a9
tracking-panda ics-tilt-tracking-gcc46-panda
aosp-panda ics-aosp-stable-gcc44-panda
staging-imx53 ics-freescalelt-stable-gcc46-imx53
panda-4.4 ics-tilt-upstream-gcc46-panda
landing-snowball ics-igloo-stable-gcc46-panda
landing-panda ics-omapzoom-stable-gcc46-panda, keep
staging-panda ics-tilt-stable-gcc46-panda
staging-origen ics-samsunglt-stable-gcc46-origen
panda ics-kwg-upstream-gcc46-panda
panda-4.4 ics-aosp-stable-gcc44-panda
Its basically,
<type of Android>-<kernel source>-<kernel type>-<toolchain
version>-<target>
Hopefully this will allow people to figure out what's what.
Comments, questions, concerns?
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
-- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android