je***********@g ehis.fr (Jerrykhan) wrote ...
Hello,
who know the best Bug tracker system on a Python/Zope server ?
BugZilla is Perl oriented (beuh !!)
What about others ?
Is A python oriented BugZilla like exists ? or need I write it ?
On a zope one or behind an apache one.
Any ideas ?
Thanks ..
BugZilla is very very heavy. It's really only applicable to very
large scale development (ie - across an enterprise, a company picky
about its progress, or very large open source projects).
If Zope is not an absolute requirement, I recommend Roundup. I used
to work with Zope corp, and still do all of my work on Zope, but we
went with Roundup for our internal bug tracking system. (We're still
hanging back on Roundup 0.5.8 or so, I haven't upgraded to 0.6). A
nice thing about Roundup is that all you need to run it is Python.
But it was the most feature complete application at the time we had to
deploy it. And for the most part, we're pretty happy with it.
I think there have been some changes to Roundup 0.6 to allow ZRoundup
to work again.
There's also Issue Dealer (this one seems actively supported, and is a
Zope product). I don't know if there's a free version or not:
http://www.nidelven-it.no/products/issue_dealer
I've written about issue trackers more than a few times on my weblog:
http://www.amber.org/mt/mt-search.cg...search=tracker
Most of the posts are pretty old by now, as we have settled on Roundup
for the time being. I'm keeping my eyes on the bug tracker being used
for Zope 3 development for possible future use:
http://www.zope3.org/tracker/
Mostly, I like its dependency tree:
http://www.zope3.org/tracker/1/@@dependencies.html
But I think it would be a fun system to play with and expand on. I'd
like to replace its dependencies system with a stronger relationship
system, and expand its security to filter out visibility for certain
tasks to certain customers while retaining a single issue database.
The problem I had when I used Zope based trackers was that it was too
easy to make custom trackers on a per project basis, making it
difficult to track "the big picture." This is more my fault than the
fault of the software though. But restricting visibility this way
made it easy to grant a customer access to a particular folder and to
a tracker inside of it, which ensured they wouldn't see (intentionally
or accidentally) data for other customers.
(We still don't have this in place with Roundup either)
--
Jeffrey P Shell
weblog:
http://toulouse.amber.org/
aud :
http://euc.cx/ 
