Threats on building models from CVS and Bugzilla repositories: the Mozilla case study

  • Authors:
  • K. Ayari;P. Meshkinfam;G. Antoniol;M. Di Penta

  • Affiliations:
  • École Polytechnique de Montréal - Canada;École Polytechnique de Montréal - Canada;École Polytechnique de Montréal - Canada;University of Sannio, Benevento, Italy

  • Venue:
  • CASCON '07 Proceedings of the 2007 conference of the center for advanced studies on Collaborative research
  • Year:
  • 2007

Quantified Score

Hi-index 0.00

Visualization

Abstract

Information obtained by merging data extracted from problem reporting systems - such as Bugzilla - and versioning systems - such as Concurrent Version System (CVS) - is widely used in quality assessment approaches. This paper attempts to shed some light on threats and difficulties faced when trying to integrate information extracted from Mozilla CVS and bug repositories. Indeed, the heterogeneity of Mozilla bug reports, often dealing with non-defect issues, and lacking of traceable information may undermine validity of quality assessment approaches relying on repositories integration. In the reported Mozilla case study, we observed that available integration heuristics are unable to recover thousands of traceability links. Furthermore, Bugzilla classification mechanisms do not enforce a distinction between different kinds of maintenance activities. Obtained evidence suggests that a large amount of information is lost; we conjecture that to benefit from CVS and problem reporting systems, more systematic issue classification and more reliable traceability mechanisms are needed.