Automated classification of change messages in open source projects

Authors:
Ahmed E. Hassan
Affiliations:
Queen's University, Kingston, Canada
Venue:
Proceedings of the 2008 ACM symposium on Applied computing
Year:
2008

Citing 7
Cited 6

RCS—a system for version control

Software—Practice & Experience
Benchmarking Kappa: Interrater Agreement in Software ProcessAssessments

Empirical Software Engineering
The dimensions of maintenance

ICSE '76 Proceedings of the 2nd international conference on Software engineering
CVSSearch: Searching through Source Code using CVS Comments

ICSM '01 Proceedings of the IEEE International Conference on Software Maintenance (ICSM'01)
Identifying Reasons for Software Changes Using Historic Databases

ICSM '00 Proceedings of the International Conference on Software Maintenance (ICSM'00)
Studying the Chaos of Code Development

WCRE '03 Proceedings of the 10th Working Conference on Reverse Engineering
Open-Source Change Logs

Empirical Software Engineering

Predicting faults using the complexity of code changes

ICSE '09 Proceedings of the 31st International Conference on Software Engineering
Identifying crosscutting concerns using historical code changes

Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
Tracing your maintenance work --- a cross-project validation of an automated classification dictionary for commit messages

FASE'12 Proceedings of the 15th international conference on Fundamental Approaches to Software Engineering
Controversy Corner: On the relationship between comment update practices and Software Bugs

Journal of Systems and Software
Controversy Corner: Preserving knowledge in software projects

Journal of Systems and Software
Revisiting prior empirical findings for mobile apps: an empirical case study on the 15 most popular open-source Android apps

CASCON '13 Proceedings of the 2013 Conference of the Center for Advanced Studies on Collaborative Research

Quantified Score

Hi-index	0.00

Visualization

Abstract

Source control systems permit developers to attach a free form message to every committed change. The content of these change messages can support software maintenance activities. We present an automated approach to classify a change message as either a bug fix, a feature introduction, or a general maintenance change. Researchers can study the evolution of project using our classification. For example, researchers can monitor the rate of bug fixes in a project without having access to bug reporting databases like Bugzilla. A case study using change messages from several open source projects, shows that our approach produces results similar to a manual classifications performed by professional developers. These findings are similar to ones reported by Mockus and Votta for commercial projects.