John Anvik
ABSTRACT
Open-source development projects typically support an open bug repository to which both developers and users can report bugs. A report that appears in this repository must be triaged to determine if the report is one which requires attention and if it is, which developer will be assigned the responsibility of resolving the report. Large open-source developments are burdened by the rate at which new bug reports appear in the bug repository. The thesis of this work is that the task of triage can be eased by using a semi-automated approach to assign bug reports to developers. The approach consists of constructing a recommender for bug assignments; examined are both a range of algorithms that can be used and the various kinds of information provided to the algorithms. The proposed work seeks to determine through human experimentation a sufficient level of precision for the recommendations, and to analytically determine the trade-offs of the various algorithmic and information choices.
- J. Anvik, L. Hiew, and G. C. Murphy. Coping with an open bug repository. In Proceedings of Eclipse Technology Exchange Workshop (eTX) at OOPSLA 2005, pages 39--43, 2005. Google Scholar
Digital Library
- J. Anvik, L. Hiew, and G. C. Murphy. Who should fix this bug? In Proceedings of the 28th International Conference on Software Engineering (ICSE'06), 2006. To appear. Google ScholarDigital Library
- I. T. Bowman and R. C. Holt. Reconstructing ownership architectures to help understand software systems. In Proceedings of International Workshop on Program Comprehension, pages 28--37, 1999. Google ScholarDigital Library
- G. Canfora and L. Cerulo. How software repositories can help in resolving a new change request. In Workshop on Empirical Studies in Reverse Engineering, 2005.Google Scholar
- D. Čubranić and G. C. Murphy. Automatic bug triage using text classification. In Proceedings of Software Engineering and Knowledge Engineering, pages 92--97, 2004.Google Scholar
- S. R. Gunn. Support Vector Machines for classification and regression. Technical report, University of Southampton, 1998.Google Scholar
- I. Guyon and A. Elissee. An introduction to variable and feature selection. Journal of Machine Learning Research, 3:1157--1182, March 2003. Google ScholarDigital Library
- T. Joachims. Text categorization with support vector machines: Learning with many relevant features. In Proceedings of the 10th European Conference on Machine Learning, pages 137--142, 1998. Google ScholarDigital Library
- A. Mockus and J. D. Herbsleb. Expertise browser: A quantitative approach to identifying expertise. In Proceedings of the 24th International Conference on Software Engineering, pages 503--512, 2002. Google ScholarDigital Library
- A. Podgurski, D. Leon, P. Francis, Wes Masri, M. Minch, Jiayang Sun, and B. Wang. Automated support for classifying software failure reports. In Proceedings of the 25th International Conference on Software Engineering, pages 465--475, 2003. Google ScholarDigital Library
- E. S. Raymond. The cathedral and the bazaar. First Monday, 3(3), 1998. Google ScholarDigital Library
- C. R. Reis and R. P. de Mattos Fortes. An overview of the software engineering process and tools in the Mozilla project. In Proceedings of the Open Source Software Development Workshop, pages 155--175, 2002.Google Scholar
- I. H. Witten and E. Frank. Data Mining: Practical Machine Learning Tools with Java Implementations. Morgan Kaufmann, 2000. Google ScholarDigital Library
Index Terms
- Automating bug report assignment
Recommendations
Improving bug triage with bug tossing graphs
ESEC/FSE '09: Proceedings of the 7th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineeringbug report is typically assigned to a single developer who is then responsible for fixing the bug. In Mozilla and Eclipse, between 37%-44% of bug reports are "tossed" (reassigned) to other developers, for example because the bug has been assigned by ...
Who should fix this bug?
ICSE '06: Proceedings of the 28th international conference on Software engineeringOpen source development projects typically support an open bug repository to which both developers and users can report bugs. The reports that appear in this repository must be triaged to determine if the report is one which requires attention and if it ...
Effective Bug Triage Based on Historical Bug-Fix Information
ISSRE '14: Proceedings of the 2014 IEEE 25th International Symposium on Software Reliability EngineeringFor complex and popular software, project teams could receive a large number of bug reports. It is often tedious and costly to manually assign these bug reports to developers who have the expertise to fix the bugs. Many bug triage techniques have been ...
Comments