Hi Ricardo, On 02/02/12 05:28, Mattias Backman wrote: > On Thu, Feb 2, 2012 at 4:24 AM, Ricardo Salveti > <ricardo.salv...@linaro.org> wrote: >> Hey, >> >> On Wed, Feb 1, 2012 at 1:54 PM, Guilherme Salgado >> <guilherme.salg...@linaro.org> wrote: >>> Hi folks, >>> >>> We're trying to make status.l.o more useful to engineers and the first >>> thing we're planning to do is a new page listing the upcoming work >>> assigned to a given person. I'm attaching a mockup of that view here and >>> we'd like to know what you think of it... Do you think that would be >>> useful to you? Is there any other information you'd like to see there, >>> or maybe a different way to present/group them? >> >> Awesome, that looks a lot better from what we have now, and easier to read. >> >> Just a few questions and comments: >> 1 - Are we tracking bugs that are not assigned to a milestone? > > The engineer's view shows upcoming work by showing the most urgent > work on top, that is by nearest deadline (unless something is > blocked). It would be tricky to determine when that work is due if a > bug is not targeted to a milestone. Perhaps all bugs assigned to this > person, but not targeted to a milestone should be listed by themselves > somewhere further down the page? > >> 2 - What will happen when the cycle is finished, but there are still >> WIs to be done? > > Our PM usually kindly reminds me about those WIs and I get the option > to complete them or split them off to a new blueprint for next cycle. > Moving the entire blueprint to the next milestone would probably be ok > too. So work items that are not done or postponed should not get stuck > on a blueprint for a finished cycle, right? > >> 3 - While I see that is useful to see what was already done for a >> cycle, for me I believe this view should behave similarly as a TODO >> list, that once something is done, it's either removed from the view, >> or changed in a way it'll not get much attention as the ones that are >> still to be done.
That's a good point, and one thing we're already doing to address that is to initially expand only the BPs that have TODO/INPROGRESS/BLOCKED work-items assigned to that person. However, if a BP has one TODO item and 10 DONE, it will be expanded and those DONE items will unnecessarily clutter the table. We could replace them all with a dummy row saying "10 more work items DONE in this BP" or something to that effect. If we do that we might not be able to allow its expansion to see all the DONE WIs, though. Cheers, -- Guilherme Salgado <https://launchpad.net/~salgado>
signature.asc
Description: OpenPGP digital signature
_______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
