[Python-Dev] Priorities in the tracker

["Martin v. Löwis"]

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)?

Regards,
Martin