On Mon, 2005-04-18 at 19:33 +0200, Magnus Hagander wrote:
> It does #7 now?! tell me how :D I've been longing for this! (I'd say
> that is one of the most important features!)
If you go to, say, the support project bug tracker:
http://pgfoundry.org/tracker/?atid=146&group_id=1000013&func=browse
there's a dropdown list at the top of the page and a textfield to put a
search keyword in. This dropdown list is context-sensitive, so if
you're viewing a forum, the "bugs" option will go away and "this forum"
or something to that effect will appear.
> >http://tinyurl.com/6v32z
>
> Hmm. Could be. I still don'tt hink it'll cut it all the wya, though.
Yup, true, probably not.
> Oh, most definitly :-) But I think we'll need something that's closer to
> "a perfect match". You need a tool that's adapted to the way the
> development works, not the other way around... Also, I'm having a hard
> time seeing this one scale to the size of postgresql (not technically -
> I'm sure it can do that, though it's dog slow on pgFoundry I'm sure it
> can be made fast on different hardware - I'm talking about
> usability-wise. The TODO list currently has somewhere around 250 items,
> and if you eventually want to bring in all bugs from pgsql-bugs etc..
Yup, PGFoundry is pretty glacial right now. It's getting put on new
hardware, though, which should help. FWIW, RubyForge (another GForge
instance) has some projects that have a fair number of items in the
trackers:
http://rubyforge.org/tracker/?atid=202&group_id=31&func=browse
and it seems to hold up fairly well.
But I agree wholeheartedly that it's better to tailor the tool to the
dev process than vice versa.
Yours,
Tom
