When do changes induce fixes?
Jacek Śliwerski, Thomas Zimmermann, Andreas Zeller · ACM SIGSOFT Software Engineering Notes · 2005
As a software system evolves, programmers make changes that sometimes cause problems. We analyze CVS archives for fix-inducing changes ---changes that lead to problems, indicated by fixes. We show how to automatically locate fix-inducing changes by linking a version archive (such as CVS) to a bug database (such as BUGZILLA). In a first investigation of the MOZILLA and ECLIPSE history, it turns out that fix-inducing changes show distinct patterns with respect to their size and the day of week they were applied.
Cited by 805 works. doi:10.1145/1082983.1083147
Authors
References
- Populating a Release History Database from version control and bug tracking systems
- Hipikat: recommending pertinent software development artifacts
- Identifying reasons for software changes using historic databases
- Preprocessing CVS data for fine-grained analysis
- Yesterday, my program worked. Today, it does not. Why?
- Analyzing and relating bug report data for feature tracking
- Toward understanding the rhetoric of small source code changes
- Visualizing software systems
- Towards understanding the rhetoric of small changes
- Project history as a group memory : learning from the past