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)

Adding a Feature


Features could come in from many sources, but ideally they should be controlled by the development team or—if they are lucky enough to have one—their development manager. Features may be suggested by users, requested by customers, or created by the developers themselves. Ultimately three decisions need to be made about each proposed feature: if, when, and who. None of these really need much explanation beyond what we have already covered in Chapter 1. However, if is worth touching on again. Not every feature should make the cut when deciding what is going to be included in our project. There are no absolute rules for this, but if we generally ask the question whether or not a feature should be included in our application, then the answer should be no. Of course this does not stop people from requesting features!

By now we should think of tickets and milestones within Trac, but we do not need a ticket for every feature. Instead, features should start out in the wiki. We need...