Shopping Cart | Login | Register | Language: English

Are Developers Fixing Their Own Bugs?: Tracing Bug-Fixing and Bug-Seeding Committers

Volume 3, Issue 2. Copyright © 2011. 20 pages.
OnDemand Article PDF Download
Download link will be e-mailed upon order completion.
$30.00
Add to Cart
DOI: 10.4018/jossp.2011040102, ISSN: 1942-3926, EISSN: 1942-3934
Sample PDFCite Article

MLA

Izquierdo-Cortazar, Daniel, Andrea Capiluppi and Jesus M. Gonzalez-Barahona. "Are Developers Fixing Their Own Bugs?: Tracing Bug-Fixing and Bug-Seeding Committers." IJOSSP 3.2 (2011): 23-42. Web. 21 May. 2012. doi:10.4018/jossp.2011040102

APA

Izquierdo-Cortazar, D., Capiluppi, A., & Gonzalez-Barahona, J. M. (2011). Are Developers Fixing Their Own Bugs?: Tracing Bug-Fixing and Bug-Seeding Committers. International Journal of Open Source Software and Processes (IJOSSP), 3(2), 23-42. doi:10.4018/jossp.2011040102

Chicago

Izquierdo-Cortazar, Daniel, Andrea Capiluppi and Jesus M. Gonzalez-Barahona. "Are Developers Fixing Their Own Bugs?: Tracing Bug-Fixing and Bug-Seeding Committers," International Journal of Open Source Software and Processes (IJOSSP) 3 (2011): 2, accessed (May 21, 2012), doi:10.4018/jossp.2011040102

Export Reference

Mendeley
Favorite
Facebook Send
Cover
Available In
Browse Subjects
Top

Abstract

The process of fixing software bugs plays a key role in the maintenance activities of a software project. Ideally, code ownership and responsibility should be enforced among developers working on the same artifacts, so that those introducing buggy code could also contribute to its fix. However, especially in FLOSS projects, this mechanism is not clearly understood: in particular, it is not known whether those contributors fixing a bug are the same introducing and seeding it in the first place. This paper analyzes the comm-central FLOSS project, which hosts part of the Thunderbird, SeaMonkey, Lightning extensions and Sunbird projects from the Mozilla community. The analysis is focused at the level of lines of code and it uses the information stored in the source code management system. The results of this study show that in 80% of the cases, the bug-fixing activity involves source code modified by at most two developers. It also emerges that the developers fixing the bug are only responsible for 3.5% of the previous modifications to the lines affected; this implies that the other developers making changes to those lines could have made that fix. In most of the cases the bug fixing process in comm-central is not carried out by the same developers than those who seeded the buggy code.
Top

Complete Article List

Volume 3: 2 Issues (2011)
Volume 2: 4 Issues (2010)
Volume 1: 4 Issues (2009)
View Complete Journal Contents Listing
Complete Journal
OnDemand Search
Search for $30 individual chapters, articles, and cases.
InfoSci-OnDemand Powered Search
Related Articles
Open Source Software Governance Serving Technological A...
© 2009, 14 pp.
Sample PDF | More details
What Makes Free/Libre Open Source Software (FLOSS) Proj...
© 2009, 13 pp.
Sample PDF | More details
Open for Social
© 2010, 16 pp.
Sample PDF | More details
Developing a Dynamic and Responsive Online Learning Env...
© 2010, 17 pp.
Sample PDF | More details
An Empirical Study of Open Source Software Usability
© 2011, 16 pp.
Sample PDF | More details
Communication Network Characteristics of Open Source Co...
© 2009, 23 pp.
Sample PDF | More details
Higher Education and FOSS for e-Learning
© 2010, 17 pp.
Sample PDF | More details