CVS for source control. No one copies code to the shared dev sandbox, qna or production. This is done via tags and a build scripts (ant).
Issue tracking: Assign one member to be Configuration Management Specialist. (CMS). A fancy CMM term to put on someones resume. Its their job to collect all open problem reports and log them. MS Excel is nice for this after you create a template.
All fixes and new bugs go through the CMS. The CMS records all activity on the bug and assigns severity and may assign someone to work on it.
Periodically have the team meet (virtual is ok) and go through the list to ensure its accurate. The team also can vote to say whether a "bug" will be fixed for this project or defered for later. (In CMM, some call the a Change Control Review Board)
The key to bug tracking is making sure there is one person responsible for the maintenance of issues. Even if you use a computer program - someBODY needs to ensure that everyone is using it correctly.
Make the spreadsheet accessible via a shared directory or web page.
The spreadsheet method works nice for *projects*. Projects meaning units of work which have defined goals, starts, ends, and defined deliverables. This technique will probably not work well for product maintenance.
-Tim
Donie Kelly wrote:
Hi all
We've been working on a project for a while and tracking details like in the
subject above are proving to be cumbersome. Is there any single tool that's
easy to install and use on a webserver (hopefully) that will manage all this
stuff for us.
Ideally, we would like to log a bug or issue and have it fixed in the
source. We might then go to this tool and check the files in so that the
tool tracks the source code changes that are made for the issue (or task or
bug etc..)
Any such tool?
Regards
Donie
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
