Difference: BugTriage (5 vs. 6)

Revision 62006-03-03 - murphy

Line: 1 to 1
 

Bug Triage

General Overview

Line: 17 to 17
 Our work as been published at a number of venues. See our publications listing below.
Added:
>
>		John Anvik, Lyndon Hiew and Gail Murphy (OK, lousy way to put people on this - other suggestions?)
 

Bug Report Assignment

Deleted:
<
<

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.
 
Changed:
<
<		For more detailed information about this project, contact John Anvik.
>
>		One step in bug triaging is assigning a developer to a newly received report. We are developing an approach for semi-automating this assignment. Our approach uses a machine-learning algorithm that is applied to the information about how bugs have been assigned in the past to recommend developers to whom a new bug should be assigned.
 
Changed:
<
<

Bug Assignment Tool

In the near future, we plan to have an assignment tool available that provides a list of recommendations for the following projects:
>
>		In the near future, we will have an assignment tool available that provides a list of recommendations for the following projects:
 
  • Eclipse Platform
  • Firefox Browser
Line: 33 to 32
 
  • A Firefox extension.
  • An Eclipse plug-in.
Changed:
<
<		Please contact John Anvik if you wish to be informed when the tool becomes available.

Using the Bug Assignment Tool with Other Projects

If you would like to use the tool for a project not listed above, please contact John Anvik. Your project must meet the following conditions for consideration:
>
>		E-mail John Anvik if you wish to be informed when the tool becomes available of if you would like to find out if you can use the tool on another project. Note, your project must meet the following conditions to be applicable for our tool:
 
  1. Uses Bugzilla (V.2.16 or higher) for tracking bug reports where the default layout for bug reports has not been altered.
  2. The project contains more than 20 developers who actively fix bugs.
  3. The project had 1000+ reports marked as FIXED in the last 8 months.
View topic | History: r8 < r7 < r6 < r5 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback