linaro-project-management team mailing list archive

[Christian Robottom Reis <kiko@xxxxxxxxxx>]

On Tue, Aug 16, 2011 at 07:21:53PM -0400, James Westby wrote:
> If they are kept up to date then you get a good picture without workitem
> information.

Right. The workitem information would be nice to have though. We could
hack that by storing that information in the milestone description,
couldn't we?

> >     - Requires all projects to be within that project group
> >     - No ordering of anything (though it does support AJAX sorting)
> 
> They are displayed in priority order aren't they? What other order would
> you want that wasn't an AJAX sort option?

I'm just referring here to the lack of explicit ranking of blueprints
and bugs. Is "ranking" clearer than "ordering"? ;-)

> >     - No view spanning milestones
> 
> What's the use case for this one?

I think I read in the other thread that we wanted to be able to see a
team's planned milestones -- in other words, being able to see in a
single page the next N milestones coming up for the team. I think this
would help with planning ahead.

> Another one is that there's no view for a month, only for a milestone.
> We've a heap of different milestones within a month right now.
> Alexnader is keen for a month view, and using the milestone page
> obviously doesn't provide that, unless we use one milestone per-month,
> and then have confusion around delivery dates.

Well, why do we have a heap of different milestones within a month?

I wonder, would this problem be solved by having something which
aggregated project groups?
-- 
Christian Robottom Reis, Engineering VP
Brazil (GMT-3) | [+55] 16 9112 6430 | [+1] 612 216 4935
Linaro.org: Open Source Software for ARM SoCs