It's not a bug, it's a feature: does misclassification affect bug localization?

CorbinSteele commented 9 years ago

Notes

Categorization: Other Authors: Pavneet Singh Kochhar, Tien-Duy B. Le, and David Lo General overview of the data:

They download Herzig et al.'s datasets which included the identiers of issue reports that they have manually analyzed. The description of that dataset follows.

The authors conducted a study on five open-source JAVA projects described in Table I (see paper). They aimed to select projects that were under active development and were developed by teams that follow strict commit and bug fixing procedures similar to industry. They also aimed to have a more or less homogenous data set which eased the manual inspection phase. Projects from APACHE and MOZILLA seemed to fit their requirements best. Additionally, they selected the five projects such that they cover atleast two different and popular bug tracking systems: Bugzilla1 and Jira2. Three out of five projects (Lucene-Java, Jackrabbit,and HTTPClient) use a Jira bug tracker. The remaining two projects (Rhino, Tomcat5) use a Bugzilla tracker. For each of the five projects, they selected all issue reports that were marked as being RESOLVED , CLOSED, or VERIFIED and whose resolution was set to FIXED and performed a manual inspection on these issues. They disregarded issues with resolution in progress or not being accepted, as their features may change in the future.The number of inspected reports per project can be found in the table above. In total, they obtained 7,401 closed and fixed issue reports. 1,810 of these reports originate from the Rhino and Tomcat5 projects and represent Bugzilla issue reports. The remaining of the 5,591 reports were filed in a Jira bug tracker. Link: It's not a bug, it's a feature: does misclassification affect bug localization? Bibtex:

@inproceedings{Kochhar:2014:BFM:2597073.2597105,
 author = {Kochhar, Pavneet Singh and Le, Tien-Duy B. and Lo, David},
 title = {It's Not a Bug, It's a Feature: Does Misclassification Affect Bug Localization?},
 booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
 series = {MSR 2014},
 year = {2014},
 isbn = {978-1-4503-2863-0},
 location = {Hyderabad, India},
 pages = {296--299},
 numpages = {4},
 url = {http://doi.acm.org/10.1145/2597073.2597105},
 doi = {10.1145/2597073.2597105},
 acmid = {2597105},
 publisher = {ACM},
 address = {New York, NY, USA},
 keywords = {Bug Localization, Misclassification},
}

Data Set:

reesjones commented 9 years ago

Needs new context notes. See this example or this example as a reference.

Context notes are directly inserted into the actual repository (like this), so good context notes are necessary for putting the datasets into the repo in a timely fashion.

reesjones commented 9 years ago

Added as bugclassify. http://openscience.us/repo/other/bugclassify.html

opensciences / opensciences.github.io

It's not a bug, it's a feature: does misclassification affect bug localization? #142

Notes