[4001] in Release_7.7_team
Re: FW: Request bug tracking db advice
daemon@ATHENA.MIT.EDU (Greg Hudson)
Sun Aug 31 01:11:42 2003
From: Greg Hudson <ghudson@MIT.EDU>
To: Mike Nolan <mknolan@mit.edu>
Cc: release-team@mit.edu
In-Reply-To: <000a01c36f6b$8ea3a920$737ba8c0@Laptop>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1062306697.19055.51.camel@error-messages.mit.edu>
Mime-Version: 1.0
Date: Sun, 31 Aug 2003 01:11:38 -0400
On Sat, 2003-08-30 at 22:57, Mike Nolan wrote:
> Oliver Thomas recommended I ask your advice on bug tracking databases.
> We're implementing one for our DOME development at MIT. I'd really
> appreciate any thoughts or experience you've had.
We use a discuss mail archive; all we keep track of is whether a bug
report has received a reply and whether it has been resolved. It works
okay for us (in a very limited sense), but we've been culturally
dependent on discuss for over a decade; I wouldn't recommend it for
anyone else.
Based on my experience and observation in the field, I agree with Oliver
on all points. I would recommend Bugzilla or RT if you're willing to
run a Linux or other Unix-type server (both can be made to run on
Windows, but neither appears well-supported on that platform), and would
probably go with Casetracker otherwise, on the theory that any
limitations it has now will likely be addressed in the near future.
