[Python-Dev] SF Priorities, 2.4 release (original) (raw)
Thomas Heller theller at python.net
Tue Aug 24 17:07:09 CEST 2004
- Previous message: [Python-Dev] SF Priorities, 2.4 release
- Next message: [Python-Dev] SF Priorities, 2.4 release
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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.
What about bugs that MUST be fixed before 2.4 final, when I don't care about the exact release they are fixed? http://python.org/sf/1014215 is such an example, imo.
Thomas
- Previous message: [Python-Dev] SF Priorities, 2.4 release
- Next message: [Python-Dev] SF Priorities, 2.4 release
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]