зеркало из https://github.com/mozilla/bugbug.git
Add more classifier to the README and sort them alphabetically
This commit is contained in:
Родитель
8cdde6e222
Коммит
31c05c9b35
28
README.md
28
README.md
|
@ -3,24 +3,36 @@
|
|||
[![Task Status](https://github.taskcluster.net/v1/repository/mozilla/bugbug/master/badge.svg)](https://github.taskcluster.net/v1/repository/mozilla/bugbug/master/badge.svg)
|
||||
|
||||
## Classifiers
|
||||
- **bug vs feature** - Bugs on Bugzilla aren't always bugs. Sometimes they are feature requests, refactorings, and so on. The aim of this classifier is to distinguish between bugs that are actually bugs and bugs that aren't. The dataset currently contains 2110 bugs, the accuracy of the current classifier is ~93% (precision ~95%, recall ~94%).
|
||||
- **assignee** - The aim of this classifier is to suggest an appropriate assignee for a bug.
|
||||
|
||||
- **defect vs feature vs task** - Extension of the previous classifier to detect differences also between feature requests and development tasks.
|
||||
- **backout** - The aim of this classifier is to detect patches that might be more likely to be backed-out (because of build or test failures). It could be used for test prioritization/scheduling purposes.
|
||||
|
||||
- **bugtype** - The aim of this classifier is to classify bugs according to their type.
|
||||
|
||||
- **component** - The aim of this classifier is to assign product/component to (untriaged) bugs.
|
||||
|
||||
- **defect vs enhancement vs task** - Extension of the **defect** classifier to detect differences also between feature requests and development tasks.
|
||||
|
||||
- **defect** - Bugs on Bugzilla aren't always bugs. Sometimes they are feature requests, refactorings, and so on. The aim of this classifier is to distinguish between bugs that are actually bugs and bugs that aren't. The dataset currently contains 2110 bugs, the accuracy of the current classifier is ~93% (precision ~95%, recall ~94%).
|
||||
|
||||
- **devdocneeded** - The aim of this classifier is to detect bugs which should be documented for developers.
|
||||
|
||||
- **duplicate** - The aim of this classifier is to detect duplicate bugs.
|
||||
|
||||
- **qaneeded** - The aim of this classifier is to detect bugs that would need QA verification.
|
||||
|
||||
- **regression vs non-regression** - Bugzilla has a `regression` keyword to identify bugs that are regressions. Unfortunately it isn't used consistently. The aim of this classifier is to detect bugs that are regressions.
|
||||
|
||||
- **regressionrange** - The aim of this classifier is to detect regression bugs that have a regression range vs those that don't.
|
||||
|
||||
- **regressor** - The aim of this classifier is to detect patches which are more likely to cause regressions. It could be used to make riskier patches undergo more scrutiny.
|
||||
|
||||
- **stepstoreproduce** - The aim of this classifier is to detect bugs that have steps to reproduce vs those that don't.
|
||||
|
||||
- **tracking** - The aim of this classifier is to detect bugs to track.
|
||||
|
||||
- **uplift** - The aim of this classifier is to detect bugs for which uplift should be approved and bugs for which uplift should not be approved.
|
||||
|
||||
- **devdocneeded** - The aim of this classifier is to detect bugs which should be documented for developers.
|
||||
|
||||
- **qaneeded** - The aim of this classifier is to detect bugs that would need QA verification.
|
||||
|
||||
- **bugtype** - The aim of this classifier is to classify bugs according to their type.
|
||||
|
||||
## Setup
|
||||
|
||||
Run `pip install -r requirements.txt` and `pip install -r test-requirements.txt`
|
||||
|
|
Загрузка…
Ссылка в новой задаче