On Mon, Oct 3, 2011 at 4:48 AM, Zach Pfeffer <zach.pfef...@linaro.org>wrote:
> On 30 September 2011 13:22, Fathi Boudra <fathi.bou...@linaro.org> wrote: > > 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 ? > > 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. > > > 2. 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. -- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
_______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
