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)

Our Feature Presentation


One popular way to view an application is as a collection of features. What are features? Features allow our application to be useful, or may even be its reason for existing. Consider the ubiquitous text editor—a pretty simple application at first glance. It not only lets us edit text, but also open, save, and print files. Of course features can have sub‑features; text editing will also include things like cut, copy, and paste, spell check, formatting, etc.

Thinking of an application in terms of features (sub-features, and sub-sub-features) allows us to break down our projects into chunks or tasks, which are much easier to manage. Of course some features will be inter-dependent, but we should consider them independent and move to the next one only when one has been completed. If the feature we want to work on depends on another feature, then we need to complete that feature. Refer back to Chapter 1 and see how thinking in terms of features fits well into our introduction...