(r3) BugTriage < SPL

Tags: view all tags
---+ Bug Triage

---++ General Overview

Open source software projects typically have a bug repository that allows 
both developers and users to post problems encountered with the software, suggest possible enhancements, and comment upon existing bug reports. Popular open source projects receive lots of bug reports. <Suggest graph here of # of bugs reported from Eclipse or Mozilla>

Since more bugs are reported than can be easily handled, each bug must be _triaged_  to determine if it describes a meaningful new problem or enhancement,
and if it does, it must be assigned to an appropriate developer for further handling.

We are investigating approaches to help automate two parts of the bug triage process:

   * [[#BugAssignment][Bug Report Assignment]]
   * [[#DuplicateDetection][Duplicate Detection]]

Our work as been published at a number of venues. See our publications listing below. 
   * [[#TriagePublications][Publications]]

#BugAssignment 
---++ Bug Report Assignment
---+++ Overview
As a means of reducing the time spent triaging and improving the triage process, we are developing and validating a machine-learning approach for semi-automating one part of the process: the assignment of a developer to a newly received report.

In the near future, we plan to have the tool available to help <hype the tool here to get people to check back later>

For more information about this subproject, contact [[http://www.cs.ubc.ca/~janvik][John Anvik]]

#DuplicateDetection 
---++ Duplicate Detection
---+++ Overview
_to be written - Lyndon_

#TriagePublications

Gail - In general, order publications by most recent first.

---++ Publications
   * [[http://www.cs.ubc.ca/labs/spl/projects/bugTriage/papers/eTx2005.pdf][Coping with Bug Repositories]], eTx Workshop at OOPSLA 2005.
   * [[http://www.cs.ubc.ca/labs/spl/projects/bugTriage/papers/icse2006.pdf][Who Should Fix This Bug?]], ICSE 2006.
Topic revision: r3 - 2006-03-02 - murphy