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)

A Common Sequence


As we have just seen, our two sequences are actually quite similar. Both require something to be reported—either a feature request or a bug, which in Trac terminology are an enhancement and a defect respectively. However both are types of ticket, and tickets equate to tasks, which is what we are aiming to manage.

Note

Tasks and tasks

When we first looked at tickets in Chapter 5, we saw that defect, enhancement, and task were default ticket types. We also use the term task in relation to project management. Fortunately we can safely avoid confusing the two—we will not be using the task ticket type in this chapter.

Once we have our ticket and we have decided that this is something we are going to tackle, then we move on to the execution of that task, and finally mark the task as complete by resolving the ticket. Here is the sequence of events, including the steps required to execute the task:

  1. 1. Raise a ticket.

  2. 2. Target to a milestone.

  3. 3. Assign to a developer.

  4. 4. Create a branch...