I love the way Trac integrates with subversion. A friend of mine even wrote a nice plugin that allows you to close a bug in Trac just by doing an svn commit, by writing stuff like:

svn commit -m "Stopped electrocuting users, fixes #4959."

Cool, we use that plugin. The only thing that annoys me is that when you're merging branches with svnmerge, it includes a copy of the log messages for all the merged revisions -- which is then processed by subversion, and has the effect of re-closing or annotating any Trac tickets mentioned in those commit messages.

Trac is perfect for us. The integration of everything in the wiki and just enough database like features makes it a killer combo for small teams (5-7). Just linking to tickets and svn changesets with wiki-like syntax is great. If you use Trac be sure to visit trac-hacks.org for plugins and macros to enhance your install.

I'm going to second Trac. I'm using it primarily because of its easy integration with Subversion.

Indeed. I just started using it, and it's quite good.

Has anyone experienced a speedup by not using the built in server?

We had it running fine under FastCGI, as well as mod_python for a few quite large projects and about 30 active developers (and a few dozen moderately active users). Speed wasn't a problem in either of those modes, but I recall that when it was straight CGI or using it's own server it was close to unusable.

I have a trac 0.94 install running on a pentium 800 through Apache and its definitely fast enough. I am not using Fast CGI though, so it could potentially be faster.

Trac is sweet but is simply a royal pain to setup.

Anyone offer an outsourced, hosted version of Trac? =)

google "trac hosting".

I use assembla.com.

Thanks =) I'll check them out!

Me too. Trac is nice if you are using Subversion.

John.