On Tue, 4 Oct 2011 18:55:24 +0200, Alexander Sack 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
On Mon, Oct 3, 2011 at 4:48 AM, Zach Pfeffer wrote:
> On 30 September 2011 13:22, Fathi Boudra 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 Dav
On Sun, 2 Oct 2011 21:48:55 -0500, Zach Pfeffer wrote:
> > 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 did
W dniu 03.10.2011 04:48, Zach Pfeffer pisze:
> On 30 September 2011 13:22, Fathi Boudra 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 an
On 30 September 2011 13:22, Fathi Boudra 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 f
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
