Populating a Release History Database from version control and bug tracking systems

Version control and bug tracking systems contain large amounts of historical information that can give deep insight into the evolution of a software project. Unfortunately, these systems provide only insufficient support for a detailed analysis of software evolution aspects. We address this problem and introduce an approach for populating a release history database that combines version data with bug tracking data and adds missing data not covered by version control systems such as merge points. Then simple queries can be applied to the structured data to obtain meaningful views showing the evolution of a software project. Such views enable more accurate reasoning of evolutionary aspects and facilitate the anticipation of software evolution. We demonstrate our approach on the large open source project Mozilla that offers great opportunities to compare results and validate our approach.

[1]  Tapani Kilpi New challenges for version control and configuration management: a framework and evaluation , 1997, Proceedings. First Euromicro Conference on Software Maintenance and Reengineering.

[2]  Harald C. Gall,et al.  Analyzing and relating bug report data for feature tracking , 2003, 10th Working Conference on Reverse Engineering, 2003. WCRE 2003. Proceedings..

[3]  Michael W. Godfrey,et al.  Secrets from the Monster: Extracting Mozilla’s Software Architecture , 2000 .

[4]  Ulf Asklund,et al.  Identifying Conflicts During Structural Merge , 1999 .

[5]  Boris Magnusson,et al.  Fine-grained revision control for collaborative software development , 1993, SIGSOFT '93.

[6]  Jan Bosch,et al.  Evolution in software product lines: Two cases , 1999 .

[7]  Harald C. Gall,et al.  Detection of logical coupling based on product release history , 1998, Proceedings. International Conference on Software Maintenance (Cat. No. 98CB36272).

[8]  E. Burton Swanson,et al.  The dimensions of maintenance , 1976, ICSE '76.

[9]  Mehdi Jazayeri,et al.  Software Architecture for Product Families: Principles and Practice , 2000 .

[10]  P. Cederqvist,et al.  Version Management with CVS , 1993 .

[11]  Harvey Siy,et al.  If your ver-sion control system could talk , 1997 .

[12]  Jan Bosch,et al.  The Evolution in Software Product Lines , 1999 .

[13]  Harald C. Gall,et al.  Visualizing software release histories: the use of color and third dimension , 1999, Proceedings IEEE International Conference on Software Maintenance - 1999 (ICSM'99). 'Software Maintenance for Business Change' (Cat. No.99CB36360).

[14]  J. Herbsleb,et al.  Two case studies of open source software development: Apache and Mozilla , 2002, TSEM.

[15]  Torsten Olsson A View of A Merge , 1996 .

[16]  Paolo Ciancarini,et al.  The evolution of configuration management and version control , 1990, Softw. Eng. J..

[17]  Harald C. Gall,et al.  Software evolution observations based on product release history , 1997, 1997 Proceedings International Conference on Software Maintenance.

[18]  Chris F. Kemerer,et al.  An Empirical Approach to Studying Software Evolution , 1999, IEEE Trans. Software Eng..