Assignment
Differences between revisions 1 and 6 (spanning 5 versions)
|
Size: 521
Comment: First Draft
|
Size: 592
Comment: Added "In Progress" infomration
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| Bug assignment in Launchpad is most commonly used to document that a team or person is Launchpad is planning on fixing the bug report. Subsequently for most packages you shoult '''not''' assign the bug to a person or team. There are some notable exceptions to this rule though. | Bug assignment in Launchpad is most commonly used to document that a team or person in Launchpad is planning on fixing the bug i.e. when the bug's status is "In Progress". Subsequently, for most packages you should '''not''' assign the bug to a person or team. There are some notable exceptions to this rule though. |
| Line 4: | Line 4: |
| * [[Include(KernelTeamBugPolicies, , from="^|| Type", to="'''ubuntu-kernel-team''' ||")]] | * [[Include(KernelTeamBugPolicies, , from="^## Assignment table included at Bugs/Assignment", to="## End of assignment")]] |
Bug assignment in Launchpad is most commonly used to document that a team or person in Launchpad is planning on fixing the bug i.e. when the bug's status is "In Progress". Subsequently, for most packages you should not assign the bug to a person or team. There are some notable exceptions to this rule though.
The Ubuntu kernel team wants bugs that are Confirmed or Triaged assigned to the appropriate kernel team.
Bugs/Assignment (last edited 2009-02-24 23:39:54 by c-76-115-103-227)