launchpad development|
Size: 1597
Comment: Work in progress
|
← Revision 15 as of 2012-06-14 15:13:12 ⇥
Size: 2561
Comment: Update blueprint link
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| '' = How to use this template = '' ''This template is for tracking what's going on with your project, especially a Launchpad feature under development. Use it to let you, your squad, the Product team and the rest of the Launchpad dev community know what's going on with your project.'' * ''Create it for your project, generally a Launchpad feature under development that has at least one LEP'' * ''Add it to [[Projects]]'' * ''Fill in the italic bits and the $VARIABLE bits'' |
|
| Line 13: | Line 3: |
| See also [[https://bugs.launchpad.net/launchpad-project/+bugs?field.tag=$PROJECT|$PROJECT bug tag]] | See also [[https://bugs.launchpad.net/launchpad-project/+bugs?field.tag=work-item-tracker|work-item-tracker bug tag]] |
| Line 16: | Line 6: |
| '''Current week:''' 2<<BR>> '''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2012-02-22 |
'''Current week:''' 17<<BR>> '''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2012-05-30<<BR>> '''Blueprint:''' https://blueprints.launchpad.net/linaro-infrastructure-misc/+spec/engineering-view-fixes <<BR>> '''Branches:''' [[https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AvOsYPy8e7yUdGkyRmx2WGFwT3NnSjdHVW04Q1pvSmc|Table with landed branches and LOC counts]] |
| Line 21: | Line 13: |
| Coming shortly. | * Provide a UI to natively support work items on blueprints. * Provide Launchpad API access to read an individual blueprint's work items. * Team and individual views showing which work items are targeted to which milestones. |
| Line 25: | Line 19: |
| ''If needed, especially if multiple LEPs'' | * Reproduce status.*.* in Launchpad. * API call to provide all work items for a project. |
| Line 27: | Line 22: |
| == Blockers == == Special actions == * Huw to review and expand on Salgado's sketch for the team overview page. |
|
| Line 35: | Line 25: |
| ''Whatever you need to keep track of deliverables. An example, including some common ones is included below. Deliverables often correspond to a group of user stories or a single user story'' |
|
| Line 38: | Line 26: |
| || Signed off LEPs || mrevell || 2012-02-15 || Drafting || ... |
|| Signed off LEPs || || || This project page serving as mini-LEP || || Work items text box in production || salgado || 2012-03-07 || DONE || || Team and individual work items view || salgado, mattias || 2012-03-07 || DONE || || Bugs and improvements || danilo, james || 2012-05-31 || INPROGRESS || |
| Line 43: | Line 33: |
| == Actions for next checkpoint == * ACTION: [mrevell] Provide text for a help pop-up to go alongside the work items text box. * ACTION: [james] Graph for the top of the engineering view mock-up. Wants to repurpose the timeline. Will demo at Linaro Connect. * ACTION: [james] "Expand all" button * ACTION: [james] create a page to show what has been done on the project so far * ACTION: [mrevell] call with Huw and James for multi-milestone work items display * ACTION: [mrevell] check what metadata Ubuntu want for work items other than headline and acceptance * ACTION: [james] Remove "Work items" text from inside the work items text box * ACTION: [mrevell] find best way to track this page as a blueprint with work items * ACTION: [danilo] Kill feedback requests on blueprints * ACTION: [mrevell] speak to Kate about migrating past blueprints: do Ubuntu want it? * ACTION: [matsubara] QA "upcoming view" page, probably after next checkpoint |
|
| Line 45: | Line 49: |
| ''Any random stuff related to the project.'' | * [[Projects/WorkItems/Checkpoint-2012-02-22]] * [[Projects/WorkItems/Checkpoint-2012-05-16]] |
| Line 47: | Line 53: |
| ''Consider also adding:'' | === Mock-ups === |
| Line 49: | Line 55: |
| * ''Link to user testing sessions'' * ''Link to exploratory testing'' * ''Link to mockups'' |
{{attachment:1.png}} {{attachment:2.png}} |
Work Items
See also work-item-tracker bug tag
Started: 2012-01-30
Current week: 17
Next checkpoint: 2012-05-30
Blueprint: https://blueprints.launchpad.net/linaro-infrastructure-misc/+spec/engineering-view-fixes
Branches: Table with landed branches and LOC counts
Scope
- Provide a UI to natively support work items on blueprints.
- Provide Launchpad API access to read an individual blueprint's work items.
- Team and individual views showing which work items are targeted to which milestones.
Out of scope
- Reproduce status.*.* in Launchpad.
- API call to provide all work items for a project.
Deliverables
Item |
Owner |
Expected date |
Status |
Signed off LEPs |
|
|
This project page serving as mini-LEP |
Work items text box in production |
salgado |
2012-03-07 |
DONE |
Team and individual work items view |
salgado, mattias |
2012-03-07 |
DONE |
Bugs and improvements |
danilo, james |
2012-05-31 |
INPROGRESS |
Feature documentation |
|
|
|
Blog post |
|
|
|
Actions for next checkpoint
- ACTION: [mrevell] Provide text for a help pop-up to go alongside the work items text box.
- ACTION: [james] Graph for the top of the engineering view mock-up. Wants to repurpose the timeline. Will demo at Linaro Connect.
- ACTION: [james] "Expand all" button
- ACTION: [james] create a page to show what has been done on the project so far
- ACTION: [mrevell] call with Huw and James for multi-milestone work items display
- ACTION: [mrevell] check what metadata Ubuntu want for work items other than headline and acceptance
- ACTION: [james] Remove "Work items" text from inside the work items text box
- ACTION: [mrevell] find best way to track this page as a blueprint with work items
- ACTION: [danilo] Kill feedback requests on blueprints
- ACTION: [mrevell] speak to Kate about migrating past blueprints: do Ubuntu want it?
- ACTION: [matsubara] QA "upcoming view" page, probably after next checkpoint
Notes
Mock-ups
