Home > Articles

The Best Software Configuration Management Tools for Cross-Platform Development Projects

In a cross-platform project, certain aspects of an SCM system take on added importance. In this chapter, the author describes the tools, including CVS, Bugzilla, Tinderbox, and Patch, that were most important to developing his Netscape and Mozilla projects.
This chapter is from the book

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:

  • Peruse the source code managed by the SCM system
  • Obtain a local copy of the source code
  • Submit modifications made to the source code by developers
  • Understand which changes have been made to the source code by developers
  • Determine the state of the source code (for example, whether it compiles)
  • 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:

  • CVS, the Concurrent Version System, which was used to maintain and manage a central copy of the Netscape/Mozilla source code
  • Bugzilla, used to track defects in programs generated from the source code stored in CVS
  • Tinderbox, used to determine the state of the source code as changes were made to the copy stored in CVS
  • 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.

Item 11: Use a Cross-Platform Bug Reporting and Tracking System

A major component of a cross-platform toolset is the bug reporting and tracking system (which I refer to as a "bug system" here for brevity). A bug system is used by developers and testers to report defects and issues encountered during the software development and testing phases of a project. In general, a bug system should allow the reporter to specify the problem encountered, identify the context or state of the system at the time the bug was discovered, and list the steps required to reproduce the bug. The bug system also must allow for the tracking of any issues it contains. In terms of tracking, bugs generally go through the following states:

  • New. A bug that has been discovered, but has not been investigated by a developer.
  • Assigned. The developer acknowledges the bug and is investigating.
  • Resolved. The developer has fixed the bug, or has some other resolution (for example, unable to reproduce the problem, or the feature is working as designed).
  • Verified. QA/test has acknowledged the resolution of the developer, and has verified it to be correct.

In addition, a bug can be in the reopened state, an indication that a once-verified bug has resurfaced in testing after originally being verified by QA.

Finally, a bug system should allow someone to specify the relative priority of bugs filed against a product. Initially, this will be the person filing the bug, but ideally, it is done in a "triage" session, with participation of the following teams: development, QA/test, and product management. Tracking priorities is not easy, it takes discipline for people to sit down for an hour or two and grind through a list of bugs, but doing so allows developers to prioritize their work, and allows those who are making ship/no-ship decisions the opportunity to objectively decide what state the project is in.

When it comes to cross-platform development, you should always look for a couple of attributes and features when selecting a bug system for use in your project.


Perhaps the most important cross-platform attribute you should look for when selecting a bug system is accessibility. In a cross-platform development project, everyone will have his or her preferred development platform (see Item 1). For some developers, it will be Mac OS X, and for many it will be Windows. If the bug system is not accessible to everyone on the team via their native platforms, it risks not being used by those who would rather not boot into one of the operating systems that the bug system does support. Therefore, the bug system itself needs to be cross-platform. And, it must support all of your tier-1 platforms.

These days, by and large, the accessibility requirement is best met by using a Web-based bug system. Web browsers are available for every platform, including PDAs and mobile phones. Bug reporting/tracking systems based on LAMP (Linux, Apache, MySQL, PHP) or Java/JSP are available.

Ability to Track Platform-Specific Bugs

In some cases, a bug will be reproducible on all platforms, and in other cases, only a subset of the supported platforms will exhibit the given problem. It is critical that the platforms affected by the problem be tracked. The bug system should allow the person filing the bug, or even someone updating the bug at a later time, to specify the platform(s) affected by any given bug. Doing so will allow someone searching the bug database to specify a subset of the supported platforms as search criteria (for example, "find all assigned Linux bugs"). By specifying the platforms as part of the search criteria, platform specialists will be able to quickly identify bugs that affect their platform, and management will be able determine the number of open (and resolved) issues on a per-platform basis.


Most of my experience with bug reporting systems has been with a bug tracking system named Bugzilla—yet another result of the Netscape/Mozilla project. Bugzilla is implemented as a Web application, allowing the database to be viewed from any platform that supports a Web browser. Bugzilla has been in active development for years, and is used by hundreds of organizations. Because Bugzilla originated during the development of the cross-platform Netscape/Mozilla system (it replaced a Netscape-internal bug system in use during the development of the 4.x browser called bugsplat), it has always supported cross-platform development directly.

Installing Bugzilla is pretty straightforward, and is well documented. A basic installation of Bugzilla can be done in about an hour, depending on your setup. (That was my experience on a stock Red Hat Fedora Core 4 system, and your results may vary.)

The following instructions are based on a Fedora Core 4 setup, using Apache and MySQL. (The default versions of Apache, Perl, and MySQL that come with FC4 are suitable for use with Bugzilla 2.22.)

Visit www.bugzilla.org, and download the latest stable release (2.22 as of this writing) onto the Linux machine that you will use to host the Bugzilla server. Then:

$ su
# tar -zxvf bugzilla-2.22.tar.gz
# mkdir /var/www/html/bugzilla
# cd bugzilla-2.22
# cp -r * /var/www/html/bugzilla
# cd /var/www/html/
# chown -R apache bugzilla
# chgrp -R apache bugzilla

The next step is to install required Perl modules. To do this, enter the following:

# perl -MCPAN -e 'install "Bundle::Bugzilla"'

You may be prompted for inputs. If so, just take whatever default responses are offered. To validate that the required modules are installed, issue the following (as root):

# cd /var/www/html/bugzilla
# perl checksetup -check-modules

When that completes, you need to rerun checksetup once again:

# perl checksetup.pl

This will create a file named localconfig. To configure Bugzilla to work with MySQL, follow the instructions at www.bugzilla.org/docs/2.22/html/configuration.html#mysql. Finally, rerun checksetup.pl one last time. The checksetup.pl script will create the Bugzilla database and prompt you for information needed to set up an administrator account in the Bugzilla database. Following this, you should be able to use the following URL to access bugzilla from your local Web browser:

  • http://localhost/bugzilla

If you have any problems with these instructions (or have a setup that differs from mine), refer to file://var/www/html/bugzilla/docs/index.html for help.

After you have installed Bugzilla, you need to add products to the bug database, and modify the list of platforms (hardware and operating systems) that can be specified when bugs are filed in the database. To do this, log in as the administrator; you should see a screen similar to the one shown in Figure 3-1.

Figure 3-1

Figure 3-1 Bugzilla main screen

In the bottom half of Figure 3-1, there is a link labeled Products. Clicking that link takes you to a screen on which you can enter the name and attributes of a product. Enter the product name and a description, accept defaults for the remaining fields, and click the Add button. You should get something like Figure 3-2.

Figure 3-2

Figure 3-2 Products screen

The next step manages the list of supported operating systems. To view the list, click the Field Values link (visible in Figures 3-1 and 3-2). Then, click the OS link in the resulting page, and you should see the list of supported operating systems (All, Windows, Mac OS, Linux, and Other, as in Figure 3-3). By clicking the operating system names to edit them, change the value Windows to Windows XP, the value Mac OS to be Mac OS X 10.4, and the value Linux to be Fedora Core 4. I personally think it is better to be fine-grained when it comes to the list of operating systems; Linux, for example, is far too vague to be truly useful. You can also add or remove operating systems using the provided controls.

Figure 3-3

Figure 3-3 Platforms screen

To modify the list of supported hardware, click the Field Values link again, click the Hardware link on the resulting page, and then modify the list of supported hardware types so that it is consistent with your supported hardware platforms. Again, being fine-grained can help in diagnosing problems. For example, instead of Macintosh, you might add choices based on type and CPU (for example, PowerBook and MacBook).

Before any bug can be filed against a product, components and version numbers need to be added for the product. This can be done by clicking the Product link, clicking the product name in the resulting table, and then clicking the Edit Components and Edit Versions links, respectively. Components are specific areas of a product. For Trixul, I defined three components: JavaScript Integration, Layout engine, and liblayout. Additional components can be added by the administrator as needed. Version numbers can be any text string that helps to identify the versions of the product; I specified 0.1.0 and 1.0. Figure 3-4 illustrates the resulting product summary page displayed by Bugzilla. As soon as at least one component and one version number has been specified, users should be able to add new bugs to the database.

Figure 3-4

Figure 3-4 Product Summary Page

Returning to the cross-platform issues of platform and hardware, let's see how they are specified by filing a bug against Trixul. One problem with Trixul is that under Microsoft Windows XP, the layout engine is built as an executable, whereas on all other platforms, the layout engine is built as a shared library that is then linked to a small executable. The reason for this bug (I believe) is a difficulty with linking a mixed (native and Common Language Infrastructure [CLI]) .NET application to a shared library using Visual Studio .NET 2003.

To file this bug, I logged on to Bugzilla, clicked the Enter a New Bug Report link, filled out the form as shown in Figure 3-5, and then clicked Commit.

Figure 3-5

Figure 3-5 Filing a new bug report

Notice how I selected Windows XP in the OS field, and PC (Intel Pentium 4) in the Platform field.

Platform-specific bugs can be easily located using the search feature of Bugzilla. To do so, visit the main Bugzilla page and click the Search Existing Bug Reports link. The resulting page allows you to specify a wide variety of search criteria, including the OS and Platform fields. Figure 3-6 illustrates a search of all open bugs filed against both Fedora Core 4 and Windows XP on the Pentium 4 platform.

Figure 3-6

Figure 3-6 Searching for bugs

If you like, you can copy and paste the URL of the search result page into a Web page or e-mail, and use that as a quick way to find all bugs related to a specific platform/operating system combination. When using Bugzilla I generally make a Web page consisting of links to all queries that I consider essential for the project I am working on; clicking a link is much easier than revisiting the Bugzilla search page and reentering all the parameters of the desired query each time I go to look at my list of bugs.

That's pretty much it for Bugzilla. Using the general guidelines I just provided, it is fairly easy to set up and maintain a database that is capable of helping you ensure that platform-specific issues are tracked accurately.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020