Jason Mills wrote:
> TortoiseSVN developers,
>
> Can I assume from proceeding email that Flyspray is used by TortoiseSVN
> as the issue tracking system?
Yes. It's here:
http://tortoisesvn.berlios.de/issues
> If so...
>
> At work we are looking for an issue tracking system. There are a lot of
> open source ones available, but most have not reached 1.0, or
> development seems to have stopped. Hence we are uncertain of there
> stability and future. Why was Flyspray chosen for the TortoiseSVN
> project? Would you recommend it over others, such as Scarab, codetrack,
> and bug genie? Any other comments.
We chose flyspray because it's written in PHP, uses MySql (which are
requirements for us, so we can install it on berlios.de and/or
sourceforge.net).
Other reasons:
- it's simple, has not zillions of features nobody ever
needs/understands/uses
- it doesn't need a masters degree to get it to run
- users can work with it immediately, no big learning curve like some
other issue trackers
- it's fast. Many operations are done without a complete reload of the
page (e.g. if you close a task, change something in a task, ... it won't
reload the whole page but simply show "task updated" at the bottom).
- it has enough user roles so that we can prevent users from creating
new issues on their own. That's why we had to get rid of the
issuetracker on tigris.org - people kept using the issuetracker to ask
questions (and most of those questions could be easily solved by reading
the docs).
btw: I've updated our issuetracker to 0.9.8 now.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sun Oct 30 17:01:22 2005