Bonsai is a web-based tool for managing . Using Bonsai, administrators can control open/closed status of trees, query a fast relational database back-end for change, branch, and comment information, and view changes made since the last time the tree was closed. These kinds of changes cause the engineer responsible to be on the hook (include cool URL link here for Hook policies at mozilla.org). Bonsai also includes gateways to and Bugzilla

CVS integration is best accomplished, at this point, using the Bugzilla Email Gateway. There have been some files submitted to allow greater CVS integration, but we need to make certain that Bugzilla is not tied into one particular software management package. Follow the instructions in the FAQ for enabling Bugzilla e-mail integration. Ensure that your check-in script sends an email to your Bugzilla e-mail gateway with the subject of [Bug XXXX] , and you can have CVS check-in comments append to your Bugzilla bug. If you have your check-in script include an @resolution field, you can even change the Bugzilla bug state. There is also a project, based upon somewhat dated Bugzilla code, to integrate CVS and Bugzilla through CVS' ability to email. Check it out at: http://homepages.kcbbs.gen.nz/~tonyg/ , under the cvszilla link.

You can find the project page for Bugzilla and Teamtrack Perforce integration (p4dti) at: http://www.ravenbrook.com/project/p4dti . p4dti is now an officially supported product from Perforce, and you can find the "Perforce Public Depot" p4dti page at http://public.perforce.com/public/perforce/p4dti/index.html . Integration of Perforce with Bugzilla, once patches are applied, is seamless. Perforce replication information will appear below the comments of each bug. Be certain you have a matching set of patches for the Bugzilla version you are installing. p4dti is designed to support multiple defect trackers, and maintains its own documentation for it. Please consult the pages linked above for further information.

We need Tinderbox integration information.