On Wed, 2009-12-02 at 12:39 +0200, Bjorn Tillenius wrote: .. > My point is that we don't really need an experiment at this point. We > already have a good idea of what needs to be done. I think the first > step is to implement tracking around teams that work both for project > groups and for projects. Then we can try it out ourselves, and when we > see that it somewhat works, we can switch to using one project only. > > Maybe the first thing to do is to look at the milestone listing for a > project group, and see how we can change it to limit bugs that are a > specific team's responsibility.
I started planning this during the last team lead meeting because I am
always contributing to many projects, and so are my team. I was
envisioning a way to see the intersection of a milestone and a team.
From my notes:
/launchpad-project/+milestone/3.1.12/+team/launchpad-registry
and
/~launchpad-registry/+milestone/launchpad-project/3.1.12
The selecting your teams from the milestone UI is doable for most
users--the insane number of teams I see looking a structural
subscriptions make me weep. Selecting a project and milestone from the
team is more difficult since we do not have a strong link from team to
project as evidence by the total work of fiction presenting or
+related-software.
As this is my personal interest, I am planning to add pillar
notification to structural subscriptions before starting milestone/team
intersections.
--
__Curtis C. Hovey_________
http://launchpad.net/
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
