linaro-project-management team mailing list archive

[David Zinman <david.zinman@xxxxxxxxxx>]

On 14 June 2012 00:48, Fathi Boudra <fathi.boudra@xxxxxxxxxx> wrote:
> On 13 June 2012 21:51, David Zinman wrote:
>> Regretfully this summary is very late.
>>
>> The Linaro 12.05 delivery cycle was fast and furious with Connect Q2.12, end of
>> quarter and delivery all occurring in the same week.
>>
>> During this 2012.05 Linaro Connect, much of the effort was focused on:
>>  *   ARM big.LITTLE implementation and testing
>>  *   Performance improvements
>>  *   Linaro-linux baseline
>>  *   Release process streamlining
>>
>> Delivery highlights can be seen at http://www.linaro.org/downloads/1205#tab1
>>
>> Platform Blueprints
>> ----------------------------
>> The number of blueprints that missed the cycle:
>> Android               18 out of 30
>> Developer Platform      6 out of 18
>> Infrastructure          5 out of 10
>> Lava                            5 out of 18
>
> We're committed to deliver only essential and high blueprints.
> Medium and Low blueprints are over-planning and nice to have.
> Wrt LAVA stats, it should be 1 out of 6 .
>
>> Total: 34 out of 76
>> 45% of blueprints scheduled for this cycle were not delivered.
>> * Not included is data from working groups and landing teams


Here are the revised numbers with only high or essential
priority blueprints:

Blueprints with High or Essential Priority
=====================================
Android                10 out of 19
Developer Platform      5 out of 16
Infrastructure          3 out of 7
Lava                    1 out of 6

Total: 19 out of 48
39% of high or essential blueprints scheduled for this cycle were not delivered.
* Not included is data from working groups and landing teams


-- 
David Zinman
Linaro Release Manager | Project Manager
Linaro.org | Open source software for ARM SoCs