Software Engineering Process and Tools in the Mozilla Project How open-source CM tools made Firefox the fastest and safest web browser

Before CM Processes  Early Mozilla development began with few formalized requirements  Many foundational codebase changes took place due to “community need”  Almost anyone could check in code  The result was chaos and gave Microsoft a 2 year headstart on Firefox  Early Mozilla development began with few formalized requirements  Many foundational codebase changes took place due to “community need”  Almost anyone could check in code  The result was chaos and gave Microsoft a 2 year headstart on Firefox

CVS  Mozilla has always used CVS as the method to alter the tree  CVS allows  Versioning  Branching  Concurrent development  Worldwide access  Preferred V&V enforcement tool  Mozilla has always used CVS as the method to alter the tree  CVS allows  Versioning  Branching  Concurrent development  Worldwide access  Preferred V&V enforcement tool

Bonsai - Graphical CVS Tool

Bonsai  Allows one to query CVS for the latest check-ins done to the repository  Shows check-in comments with hyperlinks to the Bugzilla bug that was fixed  Provides an interface to view differences between versions of files in the CVS repository  Allows visual identification of which developers are responsible for which sections of a single code file  Allows one to query CVS for the latest check-ins done to the repository  Shows check-in comments with hyperlinks to the Bugzilla bug that was fixed  Provides an interface to view differences between versions of files in the CVS repository  Allows visual identification of which developers are responsible for which sections of a single code file

Tinderbox  Tinderbox is an automated system to track compilations and tests  Red indicates compilation failed  Orange indicates compilation succeeded, but the test-suite failed  Green indicates compilation and tests ran successfully  Yellow indicates compilation is still in progress  Tinderbox is an automated system to track compilations and tests  Red indicates compilation failed  Orange indicates compilation succeeded, but the test-suite failed  Green indicates compilation and tests ran successfully  Yellow indicates compilation is still in progress

Tinderbox Screenshot Only Sheriffs can approve check-ins

Firefox Tinderbox

Bugzilla Managing Software Development

Bugzilla Features  Track bugs and code changes  Communicate with teammates  Submit and review patches  Manage quality assurance (QA)  Track bugs and code changes  Communicate with teammates  Submit and review patches  Manage quality assurance (QA)

Bugzilla Benefits  Improves communication  Increases product quality  Improves customer satisfaction  Ensures accountability  Increases productivity  Adaptable to multiple situations  Improves communication  Increases product quality  Improves customer satisfaction  Ensures accountability  Increases productivity  Adaptable to multiple situations

Summary  Anarchy reigned supreme in Mozilla prior to the use of CM tools  CVS is the process enforcement tool  Bonsai is a CVS to web interface tool  Bugzilla manages issues and enables triage  Tinderbox is software for automating verification and validation  Anarchy reigned supreme in Mozilla prior to the use of CM tools  CVS is the process enforcement tool  Bonsai is a CVS to web interface tool  Bugzilla manages issues and enables triage  Tinderbox is software for automating verification and validation