linaro-project-management team mailing list archive

[James Westby <james.westby@xxxxxxxxxx>]

On Wed, 17 Aug 2011 08:13:56 -0300, Christian Robottom Reis <kiko@xxxxxxxxxx> wrote:
> 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?

We could, but I don't think milestones have descriptions?

> > >     - 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"? ;-)

RIght, we only have the priorities.

> > >     - 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.

I've seen requests for "all the milestones this month." I can imagine
that seeing the next N may be useful on occaision, but I can't think of
a critical use case that requires it off the top of my head.

> > 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?

Due to the different delivery dates. I think we currently have

  * toolchain release
  * rest of component releases (kernel, LAVA, linaro-image-tools,
    etc.)
  * platforms release

We can use a single milestone to have them all one page, but then there
is confusion on when each thing is to be delivered. We can have a
milestone for each, but then there is no way to see everything the team
is working on this month.

> I wonder, would this problem be solved by having something which
> aggregated project groups?

This particular problem? I'm not sure. My understanding is tha the
request is to see "everything this month" along with the dates at which
each is due.

Thanks,

James