Book Image

Managing Software Development with Trac and Subversion

By : David J Murphy
Book Image

Managing Software Development with Trac and Subversion

By: David J Murphy

Overview of this book

<p><br />Trac is a minimalistic open-source enhanced wiki and bug/issue tracking system for software development projects, designed to help developers while staying out of the way and provides an interface to Subversion. Subversion is an open-source version control system that addresses many of the perceived deficiencies of CVS and can use WebDAV for network communications, and the Apache web server to provide repository-side network service.<br /><br />This book presents a simple set of processes and practices that allow you to manage these projects using open-source software without getting in the way by imposing as little as possible on established development practices and policies.<br /><br />This book looks at what is needed to manage software development projects, how web-based software project management system Trac and open-source revision control system Subversion meet these needs, and how to install, configure, and use them.</p> <p><a href="http://www.packtpub.com/article/managing-software-development-with-trac-and-subversion-table-of-contents"><br /></a></p>
Table of Contents (15 chapters)

Fixing a Bug


We need to follow a slightly different work flow for fixing a bug. Bugs—or defects in Trac terminology—should always start with a ticket, even if it is one of the developers who discovers it. New bugs should be processed on a regular basis—an activity commonly referred to as triage—with the frequency being anything from the moment each bug is reported to hourly, daily, or even weekly but we should not have a processing cycle longer than that. This process aims to answer a few immediate questions:

  • Has it been reported before?

  • Is the report valid?

  • Is it reproducible?

  • How severe is it?

Different projects may have different questions, but if we can answer these then we have a good start. The benefit of asking the first question is obvious: if a ticket for a similar bug already exists we can resolve this one as a duplicate within Trac and move on. We should remember, though, to add a comment saying which ticket this is a duplicate of. If this is genuinely a new bug then we need to establish...