Building Knowledge through Families of Experiments
IEEE Transactions on Software Engineering
Two case studies of open source software development: Apache and Mozilla
ACM Transactions on Software Engineering and Methodology (TOSEM)
An Empirical Study of Speed and Communication in Globally Distributed Software Development
IEEE Transactions on Software Engineering
Proceedings of the 28th international conference on Software engineering
Fine grained indexing of software repositories to support impact analysis
Proceedings of the 2006 international workshop on Mining software repositories
Supporting change request assignment in open source development
Proceedings of the 2006 ACM symposium on Applied computing
A Linguistic Analysis of How People Describe Software Problems
VLHCC '06 Proceedings of the Visual Languages and Human-Centric Computing
Detection of Duplicate Defect Reports Using Natural Language Processing
ICSE '07 Proceedings of the 29th international conference on Software Engineering
How Long Will It Take to Fix This Bug?
MSR '07 Proceedings of the Fourth International Workshop on Mining Software Repositories
Predicting Eclipse Bug Lifetimes
MSR '07 Proceedings of the Fourth International Workshop on Mining Software Repositories
Proceedings of the twenty-second IEEE/ACM international conference on Automated software engineering
An approach to detecting duplicate bug reports using natural language and execution information
Proceedings of the 30th international conference on Software engineering
Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement
Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering
The secret life of bugs: Going past the errors and omissions in software repositories
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
Does distributed development affect software quality? An empirical case study of Windows Vista
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
Improving bug triage with bug tossing graphs
Proceedings of the the 7th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering
Debugging in the (very) large: ten years of implementation and experience
Proceedings of the ACM SIGOPS 22nd symposium on Operating systems principles
Proceedings of the 2010 ACM conference on Computer supported cooperative work
How power users help and hinder open bug reporting
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Characterizing and predicting which bugs get fixed: an empirical study of Microsoft Windows
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
Predicting Re-opened Bugs: A Case Study on the Eclipse Project
WCRE '10 Proceedings of the 2010 17th Working Conference on Reverse Engineering
"Not my bug!" and other reasons for software bug report reassignments
Proceedings of the ACM 2011 conference on Computer supported cooperative work
Reducing the effort of bug report triage: Recommenders for development-oriented decisions
ACM Transactions on Software Engineering and Methodology (TOSEM)
Factors characterizing reopened issues: a case study
Proceedings of the 8th International Conference on Predictive Models in Software Engineering
Evolution of developer social network and its impact on bug fixing process
Proceedings of the 6th India Software Engineering Conference
Categorizing bugs with social networks: a case study on four open source software communities
Proceedings of the 2013 International Conference on Software Engineering
Bug resolution catalysts: identifying essential non-committers from bug repositories
Proceedings of the 10th Working Conference on Mining Software Repositories
Injecting mechanical faults to localize developer faults for evolving software
Proceedings of the 2013 ACM SIGPLAN international conference on Object oriented programming systems languages & applications
Hi-index | 0.00 |
Fixing bugs is an important part of the software development process. An underlying aspect is the effectiveness of fixes: if a fair number of fixed bugs are reopened, it could indicate instability in the software system. To the best of our knowledge there has been on little prior work on understanding the dynamics of bug reopens. Towards that end, in this paper, we characterize when bug reports are reopened by using the Microsoft Windows operating system project as an empirical case study. Our analysis is based on a mixed-methods approach. First, we categorize the primary reasons for reopens based on a survey of 358 Microsoft employees. We then reinforce these results with a large-scale quantitative study of Windows bug reports, focusing on factors related to bug report edits and relationships between people involved in handling the bug. Finally, we build statistical models to describe the impact of various metrics on reopening bugs ranging from the reputation of the opener to how the bug was found.