Hi Zach,
I noticed that you introduced BUGREPORTED on Android blueprints for the work items. It raised a couple of questions: 1. what does BUGREPORTED means ? 2. do we need to update https://wiki.linaro.org/Process/WorkItemsHowto#Work_items_in_the_whiteboard ?
The whiteboard work items are parsed to update status.linaro.org so I guess these work items are simply skipped.
Cheers,
On 30 September 2011 13:22, Fathi Boudra fathi.boudra@linaro.org wrote:
Hi Zach,
I noticed that you introduced BUGREPORTED on Android blueprints for the work items. It raised a couple of questions:
- what does BUGREPORTED means ?
When David Zinmann and I were going through each WI and closing out 11.09, a few BPs were done, except for one or two issues. These issues were bugs, so instead of filing a new WI in 11.10 we just marked the WI as BUGREPORTED and linked the bug to the 11.09. BUGREPORTED seemed to unambiguously mark a hand off between the BP tracking and the bug system.
- do we need to update
https://wiki.linaro.org/Process/WorkItemsHowto#Work_items_in_the_whiteboard ?
I think we should. BUGREPORTED seemed to fill a void as David and I were going through each item that the other fields didn't. For reference:
TODO empty string, INPROGRESS Item is expected to be done by the end of the cycle INPROGRESS By default, this is an alias for TODO, but teams can choose to track it separately. BLOCKED Item is still expected to be done by end of cycle, but cannot move forward due to issues outside assignees control DONE POSTPONED POSTPONE item will not be done this cycle
The whiteboard work items are parsed to update status.linaro.org so I guess these work items are simply skipped.
Cheers,
Fathi Boudra Linaro Release Manager | Validation Project Manager Linaro.org | Open source software for ARM SoCs
W dniu 03.10.2011 04:48, Zach Pfeffer pisze:
On 30 September 2011 13:22, Fathi Boudra fathi.boudra@linaro.org wrote:
Hi Zach,
I noticed that you introduced BUGREPORTED on Android blueprints for the work items. It raised a couple of questions:
- what does BUGREPORTED means ?
When David Zinmann and I were going through each WI and closing out 11.09, a few BPs were done, except for one or two issues. These issues were bugs, so instead of filing a new WI in 11.10 we just marked the WI as BUGREPORTED and linked the bug to the 11.09. BUGREPORTED seemed to unambiguously mark a hand off between the BP tracking and the bug system.
You know that linked bug counts as work item too? So if you have work item for each you reported a bug you can drop it from whiteboard once it got linked.
On Sun, 2 Oct 2011 21:48:55 -0500, Zach Pfeffer zach.pfeffer@linaro.org wrote:
- do we need to update
https://wiki.linaro.org/Process/WorkItemsHowto#Work_items_in_the_whiteboard ?
I think we should. BUGREPORTED seemed to fill a void as David and I were going through each item that the other fields didn't. For reference:
Updating the wiki page isn't all that needs to happen.
Any unknown statuses are treated by status.linaro.org as TODO, and a warning is generated to alert people to check whether that is correct and act accordingly.
If we want to use BUGREPORTED then the code will have to be changed to understand that (and map it to an existing status probably) so that the workitem counts are correct, and the warning is no longer generated.
Thanks,
James
On Mon, Oct 3, 2011 at 4:48 AM, Zach Pfeffer zach.pfeffer@linaro.orgwrote:
On 30 September 2011 13:22, Fathi Boudra fathi.boudra@linaro.org wrote:
Hi Zach,
I noticed that you introduced BUGREPORTED on Android blueprints for the work items. It raised a couple of questions:
- what does BUGREPORTED means ?
When David Zinmann and I were going through each WI and closing out 11.09, a few BPs were done, except for one or two issues. These issues were bugs, so instead of filing a new WI in 11.10 we just marked the WI as BUGREPORTED and linked the bug to the 11.09. BUGREPORTED seemed to unambiguously mark a hand off between the BP tracking and the bug system.
- do we need to update
https://wiki.linaro.org/Process/WorkItemsHowto#Work_items_in_the_whiteboard
?
I think we should. BUGREPORTED seemed to fill a void as David and I were going through each item that the other fields didn't. For reference:
TODO empty string, INPROGRESS Item is expected to be done by the end of the cycle INPROGRESS By default, this is an alias for TODO, but teams can choose to track it separately. BLOCKED Item is still expected to be done by end of cycle, but cannot move forward due to issues outside assignees control DONE POSTPONED POSTPONE item will not be done this cycle
Do we really need this kind detail encoded in the the state of a WI itself?
Alternatively, we could always add a comment to the white board to document what happened with POSTPONED work items.
On Tue, 4 Oct 2011 18:55:24 +0200, Alexander Sack asac@linaro.org wrote:
Do we really need this kind detail encoded in the the state of a WI itself?
Alternatively, we could always add a comment to the white board to document what happened with POSTPONED work items.
I agree with Alexander here, I think we can do without this state.
Would anyone object to me changing those workitems with that state to POSTPONED?
Thanks,
James
-
Alexander Sack -
Fathi Boudra -
James Westby -
Marcin Juszkiewicz -
Zach Pfeffer