Difference between revisions of "IssueHandling"
From Apache OpenOffice Wiki
(→responsible owner paradigm) |
|||
| Line 3: | Line 3: | ||
== responsible owner paradigm == | == responsible owner paradigm == | ||
| − | + | Currently every issue is assigned to an owner. There are default owners defined per project. The default owner reviews the incoming issues and is assigning the issues the the correct owners in engineering. In most cases also the target milestone will be set (next release, 3.x, Later, PleaseHelp). So some engineers have several hundred issues assigned which is an unreasonable high amount of issues. Idea is to introduce a new owner "unassigned" (nobody is already occupied in OOo) to which issues can be reassigned to indicate that anybody else is able to jump on this issue. | |
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse;" | {| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse;" | ||
| Line 18: | Line 18: | ||
|- | |- | ||
| || a developer has an reasonable amount of issues || | | || a developer has an reasonable amount of issues || | ||
| + | |- | ||
| + | | || a developer is not blocking issues || | ||
|- | |- | ||
|} | |} | ||
| − | |||
| − | |||
== y.x Targets (2.x, 3.x, etc) == | == y.x Targets (2.x, 3.x, etc) == | ||
Revision as of 12:45, 13 February 2008
Proposal for a changed issue handling
responsible owner paradigm
Currently every issue is assigned to an owner. There are default owners defined per project. The default owner reviews the incoming issues and is assigning the issues the the correct owners in engineering. In most cases also the target milestone will be set (next release, 3.x, Later, PleaseHelp). So some engineers have several hundred issues assigned which is an unreasonable high amount of issues. Idea is to introduce a new owner "unassigned" (nobody is already occupied in OOo) to which issues can be reassigned to indicate that anybody else is able to jump on this issue.
| Name | Pros | Cons |
|---|---|---|
| dedicated owner | There's every time a responsible owner to ask | there is only one owner, people dont care about issue assigned to others |
| clear responsiblity | unclear responsibilty, the project group is in charge | |
| assigned to the right person | unclear transparency, it's is unclear if the owner really intend to work on this issue in the near future | |
| issues with owner unassigned | transparency: owner do not intend to work on issue in reasonable timeframe | |
| a developer has an reasonable amount of issues | ||
| a developer is not blocking issues |
