Bringing up the monthly integration blueprint again...
We could list the builds from these pages. All of the delivered
components will hopefully be listed on the blueprint, we could also
list the test results and build instructions in one place as well as
anything else. People would be able to get everything they need in one
place.
What are monthly integration blueprints?
I've sent this text around to a few people, but here it is for everyone:
For better or worse Android builds are fairly monolithic in their
construction. There's a lot of layering violations and out-right hacks
people do to get things working.
To ship Android images everyone's going to need to pull Android
builds, integrate their changes, and test the results - especially in
the kernel, multimedia and graphics domains.
Here's what I'm thinking:
I want to create a monthly Android integration blueprint. In the
blueprint all the leads and PoCs and Landing teams will list what
they're going to deliver by the 3rd week of the month. Each team would
then take and test their changes against the latest Android build and
send the changes for integration. The changes would bake for a week
and then get released. The BP would then turn into the release note.
We are getting a Gerrit instance going to ease patch submission and
testing. Once that's working people will be able to push to it, have
their change tested across all targets and merged. Gerrit would also
be modified to track upstreaming. Until Gerrit gets going this process
will be done manually.
Any comments, questions, concerns? What this boils down to is a need
to have much closer ties between all the groups. The goal is an
Android image that has the best available components. Getting there
requires a lot of work that cuts across all domains in strange and
unforeseen ways.
-Zach
On 26 May 2011 21:00, Michael Hope <michael.h...@linaro.org> wrote:
> On Thu, May 26, 2011 at 8:54 PM, Fathi Boudra <fathi.bou...@linaro.org> wrote:
>> Hi,
>>
>> Here's the following rationale:
>> 1. 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...)
>> 2. 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
>>
>> 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.
>
> I'm quite happy with hosting our releases on Launchpad. It ties
> everything related to that product together quite well. I would like
> some type of landing page though especially when we start doing binary
> releases and if we do a toolchain stable branch.
>
> -- Michael
>
_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
