Different Bug Fixing Regimes? A Preliminary Case for Superbugs
The paper investigates the processes by which bugs are fixed in open-source software projects. Focusing on Mozilla and combining data from both its bug tracker (Bugzilla) and from its CVS, we suggest that: a) Some bugs resist beyond the first patch applied to the main branch of the source code in relation to them, which we denote as superbugs; b) There might exist different bug fixing regimes; c) priority and severity flags as defined in bug repositories are not optimized for superbugs and might lead to a involuntary side effects; d) The survival time of superbugs is influenced by the nature of the discussions within Bugzilla, by bug dependencies and by the provision of contextual elements.
KeywordsMain Branch Contextual Element Open Source Software Development Coordination Practice Information System Success
- 1.K. Crowston, J. Howison, and H. Annabi. Information systems success in free and open source software development. Software Process, In Press.Google Scholar
- 2.K. Crowston and B. Scozzi. Coordination practices for bug fixing within FLOSS development teams. In Proc. CSAC, 2004.Google Scholar
- 4.E. S. Raymond. The cathedral and the bazaar. First Monday, 3, 1998.Google Scholar
- 5.R. J. Sandusky, L. Gasser, and G. Ripoche. Bug report networks. In Proc. ICSE Workshop Mining Software Repositories, 2004.Google Scholar