RetroSearch Browse

Sun Jan 20 19:53:03 CET 2008 · https://mail.python.org/pipermail/python-dev/2008-January/076352.html

Martin v. Löwis wrote:
> 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)?
> 
It would appear useful to define some workflow aspects of issue 
processing, for example to ensure that priority gets set by a 
"responsible" reviewer.

However whether such workflow should be imposed by automation or simply 
a discipline of development I'm not in a position to say.

regards
  Steve
-- 
Steve Holden        +1 571 484 6266   +1 800 494 3119
Holden Web LLC              http://www.holdenweb.com/

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2008-January/076352.html below:

[Python-Dev] Priorities in the tracker