Difference: BugTriage (3 vs. 4)

Revision 42006-03-02 - JohnAnvik

Line: 1 to 1
 

Bug Triage

General Overview

Line: 22 to 22
 

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:
<
<		In the near future, we plan to have the tool available to help
>
>		For more detailed information about this project, contact John Anvik.

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:
  • Eclipse Platform
  • Firefox Browser

The tool will be provided in two formats:

  • A Firefox extension.
  • An Eclipse plug-in.

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:
  1. Uses Bugzilla 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.
 
Deleted:
<
<		For more information about this subproject, contact John Anvik
 

Duplicate Detection

Line: 32 to 48
 to be written - Lyndon

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

Publications

Deleted:
<
<
 
Added:
>
>

 
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