[Python-Dev] Priorities in the tracker

[Christian Heimes]

Georg Brandl wrote:
> 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.

I've defined the priorities for me:

low = nice to have feature
normal = well ... pretty normal :)
high = important, investigate the bug before the next release gets out
urgent = bug breaks development or is a show stopper
immediate = security issue or major development stopper

Christian