Home arrow Site Administration arrow Software Configuration Management

Software Configuration Management

If you want to use a software configuration management system to do cross-platform development, certain important considerations apply. This article, the first in a four-part series, takes an in-depth look at the requirements of an SCM system for cross-platform projects. It is excerpted from chapter three of the book Cross-Platform Development in C++, written by Syd Logan (Addison-Wesley; ISBN: 032124642X).

TABLE OF CONTENTS:
  1. Software Configuration Management
  2. Item 11: Use a Cross-Platform Bug Reporting and Tracking System
By: Addison-Wesley Prentice Hall PTR
Rating: starstarstarstarstar / 0
October 05, 2011

print this article
SEARCH DEV SHED

TOOLS YOU CAN USE

advertisement

A software configuration management (SCM) system consists of tools and processes used to manage the source code of a project and to assess its state. With these tools, management and developers can do the following:

  1. Peruse the source code managed by the SCM system 
     
  2. Obtain a local copy of the source code 
     
  3. Submit modifications made to the source code by developers 
     
  4. Understand which changes have been made to the source code by developers 
     
  5. Determine the state of the source code (for example, whether it compiles) 
     
  6. Log and track defects associated with binaries created from the source code

In a cross-platform project, certain aspects of an SCM system take on added importance. In this chapter, I describe the tools that were most important to Netscape and Mozilla in this regard:

  1. CVS, the Concurrent Version System, which was used to maintain and manage a central copy of the Netscape/Mozilla source code 
     
  2. Bugzilla, used to track defects in programs generated from the source code stored in CVS 
     
  3. Tinderbox, used to determine the state of the source code as changes were made to the copy stored in CVS 
     
  4. Patch, a tool that fosters the distribution and communication of changes among developers (in particular, between a developer and code reviewers) prior to it being permanently stored in CVS

These tools, combined with some best practices for using them that I describe in this chapter, helped greatly in ensuring that Netscape shipped cross-platform products that were similar in features and overall quality, and did so on the same schedule.



 
 
>>> More Site Administration Articles          >>> More By Addison-Wesley Prentice Hall PTR
 

blog comments powered by Disqus
escort Bursa Bursa escort Antalya eskort
   

SITE ADMINISTRATION ARTICLES

- Coding: Not Just for Developers
- To Support or Not Support IE?
- Administration: Networking OSX and Win 7
- DotNetNuke Gets Social
- Integrating MailChimp with Joomla: Creating ...
- Integrating MailChimp with Joomla: List Mana...
- Integrating MailChimp with Joomla: Building ...
- Integrating MailChimp with Joomla
- More Top WordPress Plugins for Social Media
- Optimizing Security: SSH Public Key Authenti...
- Patches and Rejects in Software Configuratio...
- Configuring a CVS Server
- Managing Code and Teams for Cross-Platform S...
- Software Configuration Management
- Back Up a Joomla Site with Akeeba Backup

Developer Shed Affiliates

 


Dev Shed Tutorial Topics: