Coping with an open bug repository

Abstract

Most open source software development projects include an open bug repository-one to which users of the software can gain full access-that is used to report and track problems with, and potential enhancements to, the software system. There are several potential advantages to the use of an open bug repository: more problems with the system might be identified because of the relative ease of reporting bugs, more problems might be fixed because more developers might engage in problem solving, and developers and users can engage in focused conversations about the bugs, allowing users input into the direction of the system. However, there are also some potential disadvantages such as the possibility that developers must process irrelevant bugs that reduce their productivity. Despite the rise in use of open bug repositories, there is little data about what is stored inside these repositories and how they are used. In this paper, we provide an initial characterization of two open bug repositories from the Eclipse and Firefox projects, describe the duplicate bug and bug triage problems that arise with these open bug repositories, and discuss how we are applying machine learning technology to help automate these processes.

A Survey of Test Based Automatic Program Repair

“…Taxonomies of repair techniques. 1 It is also the class that Weimer originally classified to [7] [30].…”

“…The suspicious degrees come from a statistical model, which takes a basic assumption that if a statement is executed by more failed test cases it is more probable to be faulty or more related to faults [10]. There are many approaches that automatically locate the fault in a program in recent years [1], [11]- [12] [13]. However, details of them have gone out of the scope of this paper.…”

“…In this work, we demonstrate the taxonomy of program repair in Fig. 1 and give a survey of Test Based Repair (TBR) 1 . Even there is a more comprehensive survey given by Martin [8] that covers the total fields of program repair including behavioral and state repair, we think it is still necessary to dedicatedly and concentrately survey test based methods within the behavioral repair domain.…”

Good or Bad Committers? —— A Case Study of Committer's Activities on the Eclipse's Bug Fixing Process

“…Several approaches [1], [7], [19]- [24] exist in this topic. For instance, Anvik et al [19], [20] proposed an approach to assign a bug to an appropriate developer based on past bug reports with natural language processing.…”

“…For instance, Anvik et al [19], [20] proposed an approach to assign a bug to an appropriate developer based on past bug reports with natural language processing. Jeong et al [1] also tried to establish a method for the bug assignment based on a social graph which reflects on social relationships among developers in the bug assignment.…”