Assignment

Differences between revisions 2 and 7 (spanning 5 versions)
⇤ ← Revision 2 as of 2007-12-04 19:37:14 →
Size: 525
Editor: c-71-59-213-167
Comment:
← Revision 7 as of 2008-05-30 20:09:52 → ⇥
Size: 647
Editor: c-24-21-234-111
Comment:
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 3: Line 3:
 * The Ubuntu kernel team wants bugs that are '''Confirmed''' or '''Triaged''' assigned to the appropriate kernel team.
  * [[Include(KernelTeamBugPolicies, , from="^\|\| Type", to="'''ubuntu-kernel-team''' \|\|")]]		  * The Ubuntu kernel team wants kernel bugs (i.e. the packages linux-source-2.6.x or linux) that are '''Confirmed''' or '''Triaged''' assigned to the appropriate 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.

CategoryBugSquad

Bugs/Assignment (last edited 2009-02-24 23:39:54 by c-76-115-103-227)