The canonical example of a project that uses trac is Sage: http://trac.sagemath.org/sage_trac It has good email integration (notify on ticket modification, etc, although it is supposed to be even better in the next version). Normally we attach patches to a ticket and then just comment them in the ticket associated with the patch. This associates the bug/feature ticket with the patch (as opposed to needing two systems if you went with something like codeview + launchpad). Compared to trac, launchpad is slow for webpage response time. It is also slow on ticket creation time (I can create a ticket for a given item in maybe 30 seconds on one page in trac, whereas launchpad has so much complexity it is significantly more time consuming, requires a multipage creation step, etc).
--Gary On Sun, May 4, 2008 at 6:58 AM, Stefan Behnel <[EMAIL PROTECTED]> wrote: > Hi, > > Gary Furnish continues to top-post: > > > Why not just use trac? The interface is much nicer [...] (and we > > > could easily host it too). It is not integrated with svn like > > codereview is, but it does have the online patch viewer functionality, > > Hmm, I never used that. Would you know an example to look at? Is it just a > patch "viewer" or can you add comments? And if so, at what granularity? Per > patch? Per line? > > > > > and using trac saves us from having to port some other solution to hg. > > that is definitely a plus. > > > > > the slow and unfriendly launchpad > > Interesting. Why do you think so? > > Stefan > > _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
