[Cython] code review

[Kirill Smelkov]

В сообщении от Воскресенье 04 мая 2008 Gary Furnish написал(a):
> 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).

I'd like to clarify what I mean saying "good email integration":

  Good email integration is two-way

That is:

-> it is possible to affect state of the issues, add comments to patch review,
   etc... by sending mail.
<- you get notification mails, when someone changes something through web
   interface, or another way.


Personally, I think having the first entry is important - a lot of tasks could
be done via plain emails, and at least some people are more productive with
keyboard & text editor (compared to clicking with mouse) :)

Does Trac have two-way email integration?



> 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, All, imagine you could create a patch issue with plain 'hg email',
or create new issue with just sending mail to special address.

Isn't this cool!?

Roundup has this now and it works. Also, although Roundup is not so shiny,
it was choosen as the tracker for Python itself:

http://bugs.python.org/

What do you think?