On Wed, Dec 2, 2009 at 1:50 AM, Martin Pool <[email protected]> wrote: > 2009/12/1 Danilo Šegan <[email protected]>: >> Hi all, >> >> У пет, 27. 11 2009. у 08:19 +0200, Bjorn Tillenius пише: >>> Personally, I think a more useful experiment would be to try out >>> different hypothesis, which doesn't make the whole team unproductive >>> for a few cycles. One hypothesis is that we need to get views for a >>> single team. Let's implement views for teams for milestones, assigned >>> bugs, subscribed bugs, and so on. Then have one team try it out and >>> see how it works. We could do this in /launchpad-project, since this >>> feature should work for both projects and project groups. >> >> Everyone from the LP side seems to be proposing something that would >> brings us back to where we start :) Eg. team-based milestones, or >> per-team tags as Tim suggests. > > It seems to me that Robert's experiment has gathered some data, and > that is: Launchpad's bug tracker doesn't scale at the moment to > handling single projects that are so large that people can't cope with > seeing the whole flow of bugs. The only way to cope with them is, as > Launchpad does, to create sub-projects for functional or > organizational areas. Doing so has some drawbacks but they are > manageable. >
Yes. > Since Launchpad's focus at the moment is on Ubuntu connections to > upstream this bug doesn't seem either critical or strategic. > > Perhaps a larger problem is that the workaround used by Launchpad is > not available to other projects, since subprojects as organizational > structure are (at least in theory) banned. Perhaps that should be > relaxed? > I think that's a good next step. But let's not give up on making Launchpad awesome. jml _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
