On 11 May 26, Fathi Boudra wrote:
Hi,
Here's the following rationale:
- as a user, I would like to easily find the released Linaro components:
- Linaro Evaluation Build (Android and Ubuntu LEB)
- Tools (linaro-image-tools)
- Working Groups (kernel, u-boot, gcc, gdb, qemu, powerdebug, powertop, etc...)
- as a user, I would like to download the release for my ${board} in
one central place. 3. as a release manager on the road to monthly releases, I would like to adjust the current layout to match the release process.
The current layout has some issues:
- a user should go through several paths to get a rootfs and a hardware pack.
- a user should go through several websites to find Linaro goods
(releases.l.o, launchpad.net)
- newcomers like Android doesn't fit well
- every team has a different release process
+1
The current layout assumes that outsiders know exactly what all our codenames mean - alip, nano, headless, developer, hwpack, etc. (!)
Hell, even I don't know what the differences are.
To resolve these user stories, we came up with 2 layouts proposal. Please, see the document attached. Feebdacks/suggestions on the proposals are welcome!
Note: we planned to start with platform directory only. The working-groups could come later when we agree on the approach.
Cheers,
Fathi
Linaro Release Manager | Platform Project Manager
==== releases.linaro.org current layout ====
platform/linaro-n |-- platform/linaro-n/alip | |-- platform/linaro-n/alip/beta-2 | `-- platform/linaro-n/alip/latest -> beta-2 |-- platform/linaro-n/android | |-- platform/linaro-n/android/11.04 | | |-- platform/linaro-n/android/11.04/beaglexm | | `-- platform/linaro-n/android/11.04/panda | `-- platform/linaro-n/android/latest -> 11.04/ |-- platform/linaro-n/developer | |-- platform/linaro-n/developer/beta-2 | `-- platform/linaro-n/developer/latest -> beta-2 |-- platform/linaro-n/hwpacks | |-- platform/linaro-n/hwpacks/beta-2 | `-- platform/linaro-n/hwpacks/latest -> beta-2 |-- platform/linaro-n/nano | |-- platform/linaro-n/nano/beta-2 | `-- platform/linaro-n/nano/latest -> beta-2 `-- platform/linaro-n/ubuntu-desktop |-- platform/linaro-n/ubuntu-desktop/alpha-3 |-- platform/linaro-n/ubuntu-desktop/beta |-- platform/linaro-n/ubuntu-desktop/beta-2 `-- platform/linaro-n/ubuntu-desktop/latest -> beta-2
==== releases.linaro.org layout proposal 1====
platform |-- platform/11.05 | |-- platform/11.05/android | | |-- platform/11.05/android/beaglexm | | |-- platform/11.05/android/ndk | | |-- platform/11.05/android/panda | | |-- platform/11.05/android/sdk | | `-- platform/11.05/android/toolchain | |-- platform/11.05/tools | | |-- platform/11.05/tools/linaro-image-tools | `-- platform/11.05/ubuntu | |-- platform/11.05/ubuntu/panda | | |-- platform/11.05/ubuntu/panda | | `-- platform/11.05/ubuntu/snowball | `-- platform/11.05/ubuntu/snowball [-- platform/11.06 `-- platform/latest -> 11.06
working-groups |-- working-groups/11.05 | |-- working-groups/11.05/graphics | |-- working-groups/11.05/kernel | |-- working-groups/11.05/multimedia | |-- working-groups/11.05/power-management | `-- working-groups/11.05/toolchain
You're again forcing people to know the difference between platform and working groups' output. None of the upstreams that we invited to Budapest knew the difference (or cared for that matter). I suspect the same is true for some of our consumers.
|-- working-groups/11.06 | |-- working-groups/11.06/graphics | |-- working-groups/11.06/kernel | |-- working-groups/11.06/multimedia | |-- working-groups/11.06/power-management | |-- working-groups/11.06/toolchain `-- working-groups/latest -> 11.06
==== releases.linaro.org layout proposal 2 ====
platform |-- platform/android | |-- platform/android/11.05 | | |-- platform/android/11.05/beaglexm | | `-- platform/android/11.05/panda | |-- platform/android/11.06 | | |-- platform/android/11.06/beaglexm | | `-- platform/android/11.06/panda | `-- platform/android/latest -> 11.06 |-- tools/linaro-image-tools | |-- tools/linaro-image-tools/0.4.7 | |-- tools/linaro-image-tools/0.4.8 | `-- tools/linaro-image-tools/latest -> 0.4.8 `-- platform/ubuntu |-- platform/ubuntu/11.05 | |-- platform/ubuntu/11.06/panda | `-- platform/ubuntu/11.06/snowball |-- platform/ubuntu/11.06 | |-- platform/ubuntu/11.06/panda | `-- platform/ubuntu/11.06/snowball `-- platform/ubuntu/latest -> 11.06
working-groups |-- working-groups/graphics | |-- working-groups/graphics/11.05 | |-- working-groups/graphics/11.06 | `-- working-groups/graphics/latest -> 11.06 |-- working-groups/kernel | |-- working-groups/kernel/11.05 | |-- working-groups/kernel/11.06 | `-- working-groups/kernel/latest -> 11.06 |-- working-groups/multimedia | |-- working-groups/multimedia/11.05 | |-- working-groups/multimedia/11.06 | `-- working-groups/multimedia/latest -> 11.06 |-- working-groups/power-management | |-- working-groups/power-management/11.05 | |-- working-groups/power-management/11.06 | `-- working-groups/power-management/latest -> 11.06 `-- working-groups/toolchain |-- working-groups/toolchain/11.05 |-- working-groups/toolchain/11.06 `-- working-groups/toolchain/latest -> 11.06
If I were an outsider, what I'd really like is this:
1. Go to releases.linaro.org 2. Click on LATEST 3. Get a directory with links to the latest of everything: hwpacks, toolchain, powedebug, etc. Also, these names should not contain version info. So, linaro-toolchain-latest.tar.gz and not linaro-toolchain-4.6.x.tar.gz 4. Now I can write a simple script that rsyncs releases.linaro.org/latest every month. We should probably just supply that script too.
There should also be a webpage under the directory listing (I believe apache can do that) that explains what the various names mean - alip vs. nano vs. developer vs. headless, etc.
OTOH, providing TestDrive would be the best solution. (I didn't know it was being taken up finally this cycle. I've now subscribed to the wiki page)
Regards, Amit