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
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
Source: https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AjEaTwrvj1bidDBIMz...
Roadmap End Of Quarter ------------------------------------- Android - 5 Cards, 5 Delivered Dev Platform - 5 Cards, 3 Delivered Graphics WG - 3 Cards, 3 Delivered Kernel WG - 4 Cards, 3 Delivered LAVA - 3 Cards, 2 Delivered Multimedia WG - 3 Cards, 1 Delivered OCTO - 2 Cards, 2 Delivered Power Management WG - 5 Cards, 5 Delivered
Total 29 Cards, 24 delivered or probably delivered.
Source: https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AmTRRvye9pnjdGJaVD...
On Wed, Jun 13, 2012 at 8:51 PM, David Zinman david.zinman@linaro.org 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
Here, I am currently not sure what to do with those numbers. Basically, I am not so much worried about low/medium blueprints that didn't get delivered. Any way we could get those numbers broken down by priority? Or just a view on our delivery rates for essential and high blueprints?
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
On 14 June 2012 00:48, Fathi Boudra fathi.boudra@linaro.org 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
-
Alexander Sack -
David Zinman -
Fathi Boudra