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)

Tagging a Release


When we have completed all the features and bugs for a milestone it is time to release. This will consist of actions like testing, quality assurance, packaging, and distribution, but here we are only concerned with one: tagging. This allows us to capture a snapshot of our Subversion repository at that moment in time that is subsequently easy to return to. We could just work with revision numbers and remember each one for future reference, but tags make the process friendly and give a feeling of accomplishment. Without tags the code will seem in a constant state of flux, whereas with them we have solid points of reference.

Creating a tag has the same process as branching, which was described in Chapter 6, except that we place them in the tags path rather than branches. Tag names should correspond to the milestones we have defined in Trac.