[Python-Dev] Priorities in the tracker

[Georg Brandl]

Martin v. Löwis schrieb:
> After some months of tracker operation, I'd like to discuss one aspect
> of the tracker schema: priorities.
> 
> Each issue has a severity and a priority. The severity is assigned by
> the submitter, defaults to normal, and indicates how serious the issue
> impacts him and the community.
> 
> The priority is assigned by a developer (and cannot be set by
> a "mere" user), and indicates how quickly this issue must be processed.
> The priority is initially unset, requiring a developer to perform screening.
> 
> It appears that developers rarely set the priority, leaving the issues
> formally unscreened.
> 
> So what should we do? Leave things as-is? Drop the notion of priority?
> Change our process to make sure priorities do get set (and honored)?

Christian currently does a good job of assigning the correct properties
to new bugs. In any case, I'd prefer to keep a way to mark a bug as
"high-priority" (meaning that it should be fixed before the next release)
even if most of the bugs don't have an assigned priority.

As to whether we need both severity and priority, I have no opinion.

Georg


-- 
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall be four. Eight shalt thou not indent, nor either indent thou
two, excepting that thou then proceed to four. Tabs are right out.