@conference {Sliwerski:2005:CIF:1083142.1083147, title = {When do changes induce fixes?}, booktitle = {Proceedings of the 2005 international workshop on Mining software repositories}, series = {MSR {\textquoteright}05}, year = {2005}, pages = {24-28}, publisher = {ACM}, organization = {ACM}, address = {New York, NY, USA}, abstract = {As a software system evolves, programmers make changes that sometimes cause problems. We analyze CVS archives for fix-inducing changes{\textemdash}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.}, keywords = {bugzilla, change analysis, cvs, eclipse, evolution, mozilla}, isbn = {1-59593-123-6}, doi = {http://doi.acm.org/10.1145/1082983.1083147}, url = {http://doi.acm.org/10.1145/1082983.1083147}, attachments = {https://flosshub.org/sites/flosshub.org/files/24WhenDoChanges.pdf}, author = {Sliwerski, J and Zimmermann, Thomas and Zeller, Andreas} }