Handling trackers

From FreeMind

Jump to: navigation, search
(Added owners for each category)
(Add priority proposal)
Line 35: Line 35:
==Categories in Bugs tracker==
==Categories in Bugs tracker==
 +
 +
Categories allow us to assign per default bugs to a certain developer, as documented in the following table.
 +
 +
; Note : the Sourceforge Tracker allows theoretically to assign automatically bugs with a certain category to a certain developer, but the feature seems slightly broken, so it's more secure to assign category ''and'' developer to a bug.
 +
{| {{Table style}}
{| {{Table style}}
! Category
! Category
Line 63: Line 68:
|-
|-
| Windows || dpolivaev
| Windows || dpolivaev
 +
|}
 +
 +
== Priority ''<<Proposal>>'' ==
 +
 +
The purpose of the priority is to make decision easier if a bug can remain open for a specific release or not, according to the following rules:
 +
 +
* priority > 5 - the bug must be closed before the next FreeMind release
 +
* priority < 5 - the bug can remain open through a release cycle
 +
* priority = 5 - 5 is the default bug value and can't have a special meaning, hence the bug must be assessed
 +
 +
Determining the priority works as follows:
 +
# determine the priority based on the type of the bug.
 +
# correct this priority based on the presence of a workaround and the number of users impacted.
 +
# if you get 5 as priority, use your judgment to correct up or down (could you live with this bug?)
 +
# after each FreeMind release, raise the priority by 1 (skipping 5).
 +
 +
{| {{Table style}}
 +
! width="20%"|Type of bug
 +
! width="70%"|Explanation
 +
! width="10%"|Priority
 +
|-
 +
| Data loss || user can loose data due to the bug || 7
 +
|-
 +
| Availability || FreeMind itself or certain functions can't be used || 5
 +
|-
 +
| Reliability or Performance || FreeMind crashes or certain functions do not always work, or only with limited speed || 4
 +
|-
 +
| Feature bugs || certain features of a function can't be used or only in a limited way (such bugs can be suspect to be enhancement requests) || 3
 +
|}
 +
&nbsp;
 +
{| {{Table style}}
 +
! width="20%"|Workaround Presence
 +
! width="70%"|Explanation
 +
! width="10%"|Priority Correction
 +
|-
 +
| No workaround || || +1
 +
|-
 +
| Any workaround || || 0
 +
|-
 +
| Definitive workaround || A definitive workaround is one that you apply once and then you're protected ''forever'' against data loss; avoiding to do something wouldn't be definitive, changing a configuration parameter would be so, being able to repair a corrupted FreeMind file as well || -1
 +
|}
 +
&nbsp;
 +
{| {{Table style}}
 +
! width="20%"|Users impacted
 +
! width="70%"|Explanation
 +
! width="10%"|Priority Correction
 +
|-
 +
| All || All users on one or more platforms || +2
 +
|-
 +
| Many || Many users, due to a common configuration || +1
 +
|-
 +
| Few || Few users, having a slightly uncommon but meaningful setup || 0
 +
|-
 +
| Very few || Very few users, having a rather meaningless setup, possibly not worth being supported by FreeMind || -1
|}
|}

Revision as of 16:00, 21 March 2008

Personal tools