Software development is not just about writing code - we need to manage the entire process.
This book looks at that process, how it can be managed, and how Trac and Subversion can help us achieve this. It combines theory with practical knowledge and experience that most developers will relate to.
Trac is an open-source, web-based project management and bug-tracking tool. Trac is an enhanced wiki and issue-tracking system for software development projects. Trac uses a minimalistic approach to web-based software project management. Trac is written in the Python programming language. In computing, Subversion (SVN) is a version control system (VCS). It allows users to keep track of changes made to any type of electronic data, typically source code, web pages, or design documents.
Chapter 1 covers the basics of task management and how these apply to software development. It also looks into another important skill needed for managing projects—communication—and discusses the problems faced during software development and how they can be solved.
Chapter 2 introduces the various applications used for implementing the solution discussed in the chapter. Trac and Subversion are the main parts of the solution, but by no means the only ones.
Chapter 3 along with the appendices shows how to install these applications on Microsoft Windows or Linux.
Chapter 4 discusses how to create and use documentation using Trac.
Chapter 5 brings us back to the topic of task management and we again focus on Trac and how it helps us with this.
Chapter 6 explores the basics of using Subversion and looks at how it integrates with Trac.
Chapter 7 shows how Trac and Subversion can be used together to manage the the two most frequent events in the development cycle of an application—fixing a bug and implementing a new feature.
Appendix A covers detailed, step by step instructions for installing Subversion on your system, and cover Microsoft Windows and Linux.
Appendix B covers detailed, step by step instructions for installing the Apache web server on your system, and covers Microsoft Windows and Linux
Appendix C covers detailed, step by step instructions for installing the Apache web server on your system, and covers Microsoft Windows and Linux
This book is for developers of all calibres, and particularly those that lead teams or projects, especially if they have recently moved into the role or are simply looking for a "better way".
In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.
There are three styles for code. Code words in text are shown as follows: "The -m "Initial repository structure" specifies a log message for the action(s) we are performing—creating folders in this fashion is actually checking in the changes directly on the server."
A block of code will be set as follows:
[ticket] default_component = default_milestone = default_priority = major
When we wish to draw your attention to a particular part of a code block, the relevant lines or items will be made bold:
Password for 'jdoe': Authentication realm: <http://projects.example.com:80> Subversion Repositories Username: [email protected] Password for '[email protected]': Path: sandbox
Any command-line input and output is written as follows:
# svn mkdir http://servername/svn/sandbox/trunk
http://servername/svn/sandbox/tags
http://servername/svn/sandbox/branches
-m "Initial repository structure"
New terms and important words are introduced in a bold-type font. Words that you see on the screen, in menus or dialog boxes for example, appear in our text like this: "clicking the Next button moves you to the next screen".
Feedback from our readers is always welcome. Let us know what you think about this book, what you liked or may have disliked. Reader feedback is important for us to develop titles that you really get the most out of.
To send us general feedback, simply drop an email to <[email protected]>, making sure to mention the book title in the subject of your message.
If there is a book that you need and would like to see us publish, please send us a note in the SUGGEST A TITLE form on www.packtpub.com or email <[email protected]>.
If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide on www.packtpub.com/authors.
Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.
Although we have taken every care to ensure the accuracy of our contents, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in text or code—we would be grateful if you would report this to us. By doing this you can save other readers from frustration, and help to improve subsequent versions of this book. If you find any errata, report them by visiting http://www.packtpub.com/support, selecting your book, clicking on the Submit Errata link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata added to the list of existing errata. The existing errata can be viewed by selecting your title from http://www.packtpub.com/support.
You can contact us at <[email protected]> if you are having a problem with some aspect of the book, and we will do our best to address it.