Hear us Roar
Article:
 |
|
Bug Trackers: Do They Really All Suck?
|
| Subject: |
|
bugtracker TRAC rocks |
| Date: |
|
2005-12-28 12:04:51 |
| From: |
|
ttriche
|
Response to: bugtracker TRAC rocks
|
|
You set up the Trac commit hook, and it parses your log messages.
Then when you write "fixes bugs #123 #456 and #789" in your commit message, that changeset gets hyperlinked to the bug and the bug is automatically closed. Trac's integration with SVN is very tight and well executed. If you already have svn2rss or email commit messages set up, adding another commit hook is trivial. If not, read the instructions.
Trac owns. If you haven't tried it, you won't understand. This article displayed an amazing amount of ignorance considering the wide uptake of Trac among popular projects. There is a Ruby version underway (Collaboa) which basically mirrors Trac with some Rails-ish integration, although FWIW, Rails uses Trac. But lately the development of Trac has progressed to refactoring and modularizing everything, rather than massive new features. To me, that is a very good sign.
There are things that suck about Trac, but compared to every other bugtracker I have ever used (bugzilla, mantis, jira) they are so miniscule as to be almost irrelevant.
|
Showing messages 1 through 1 of 1.
-
bugtracker TRAC rocks
2006-10-27 06:02:41
joedayney
[View]
|
| |
New to all of this and have got SubVersion set up and TortoiseSVN and have Trac set up and would like to integrate Trac to SubVersion ... looked at the Docs but would be greatful for info on the steps to set up. Thanks.
Joe