<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sliwerski, J</style></author><author><style face="normal" font="default" size="100%">Zimmermann, Thomas</style></author><author><style face="normal" font="default" size="100%">Zeller, Andreas</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">When do changes induce fixes?</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2005 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '05</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bugzilla</style></keyword><keyword><style  face="normal" font="default" size="100%">change analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">mozilla</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1082983.1083147</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/24WhenDoChanges.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">24-28</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-123-6</style></isbn><abstract><style face="normal" font="default" size="100%">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.</style></abstract></record></records></xml>
