Home Original page

[Python-Dev] SF Priorities, 2.4 release

Kurt B. Kaiser kbk at shore.net
Tue Aug 24 16:09:33 CEST 2004 
Anthony Baxter <anthony at interlink.com.au> writes:

> Working originally from Tim's list, I propose to start using the
> priorities in the SF tracker to try and manage the outstanding work
> for 2.4. Here's the proposed list:
>
> Priority 9:
>    - MUST be done before the next release (whether it's a3, b1, b2,
>      or whatever)
> Priority 8:
>    - MUST be done before b1. It's a functionality change, and it's
>      needed for 2.4. If it's not done before b1, it will have to wait
>      until 2.5, whenever that might be.
> Priority 7:
>    - SHOULD be done before 2.4 final.
>
> I'm going to go through and start updating various open bugs and
> patches with priorities.
>
> How can you help? I'd _really_ prefer that people not run around
> setting priorities themselves - instead, if you could let me know
> of bugs/patches that you think should be changed, let me know,
> either via email, or via IRC - #python-dev on irc.freenode.net.

OK, but how about a further tweak (I use priorities to manage IDLE):

Priorities 7 - 9 are reserved and modifiable only by the Release Manager.

Priorities 6 and below are not reserved and may be modified as desired
within the range 1 - 6.

-- 
KBK
More information about the Python-Dev mailing list