On Mon, Mar 17, 2008 at 9:10 PM, Brett Cannon <[EMAIL PROTECTED]> wrote: > Barry, Neal, and myself had a conversation and changed the priority > fields in the tracker. You can click on 'priority' to see an > explanation, but the new fields are: > > - release blocker > - critical > - high > - normal > - low > > So "release blocker" blocks a release. "Critical" could very easily > block a release, but not the current one. "High" issues should be > addressed, but won't block anything. "Normal" is normal. And "low" is > for spelling errors and such.
Primarily everyone should use normal for issues that are, uh, normal. "Critical" should be used for bugs that are things like: crashing the interpreter, serious memory/reference leaks. "High" could be used for large problems with resource usage (too much memory) or something that is otherwise, important. n _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
