Release Management needs the list of the the blueprints that will be delivered this month. For each bp, they want a Headline and Acceptance criteria. The Headline is a statement to include in the Monthly release announcement. The acceptance criteria is a statement how to verify the work is done.
I have collected this month's blueprints in the spreadsheet, please review it for accuracy. If a blueprint you are working on is missing, please add it.
The Headline and Acceptance can be added into the whiteboard as follows: Headline: headline text
Acceptance: acceptance text
Once you add the the headline and acceptance, please modify the spreadsheet to reflect that it is done. https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AoZqvK7R1biJdGxScl...
Thanks in advance, Mounir
On Wed, Sep 07, 2011 at 01:05:20PM -0500, Mounir Bsaibes wrote:
Once you add the the headline and acceptance, please modify the spreadsheet to reflect that it is done. https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AoZqvK7R1biJdGxScl...
Blueprint health check FTW!
On Thu, Sep 8, 2011 at 6:05 AM, Mounir Bsaibes mounir.bsaibes@linaro.org wrote:
Release Management needs the list of the the blueprints that will be delivered this month. For each bp, they want a Headline and Acceptance criteria. The Headline is a statement to include in the Monthly release announcement. The acceptance criteria is a statement how to verify the work is done.
I have collected this month's blueprints in the spreadsheet, please review it for accuracy. If a blueprint you are working on is missing, please add it.
The Headline and Acceptance can be added into the whiteboard as follows: Headline: headline text
Acceptance: acceptance text
Once you add the the headline and acceptance, please modify the spreadsheet to reflect that it is done. https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AoZqvK7R1biJdGxScl...
I've bitten the bullet and split the work item blocks out into blueprints. You can see the blueprints against this month at: https://launchpad.net/linaro-toolchain/+milestone/4.6-2011.09 https://launchpad.net/linaro-toolchain/+milestone/7.3-2011.09 https://launchpad.net/linaro-toolchain/+milestone/2011.09
and the backlog across the group or project at: https://launchpad.net/linaro-toolchain/+milestone/backlog https://launchpad.net/gcc-linaro/+milestone/backlog
Some of the high priority backlogs need a bit more splitting.
I've used Delivery = 'Beta Available' as some type of 'almost done'. For the remote watchpoint blueprint, this means 'done, backported, will upstream next week'. For one of Ira's blueprints it means 'done, upstream, in the shake down time, not backported'.
Here's a tricky one: https://blueprints.launchpad.net/gdb-linaro/+spec/gdb-server-completeness
It has one work item that is done. The remaining work is tracked through bugs. I've deleted the milestone.
I've deleted the acceptance line on all performance blueprints. The acceptance criteria for these is upstreamed and backported, and it's better for this to be implicit than redundant. I've deleted the headlines on any where the headline is the past tense version of the title.
-- Michael
linaro-toolchain@lists.linaro.org