[Python-Dev] 2.4a3 release is September 2, SF tracker keywords
anthony at interlink.com.au
Thu Aug 19 17:50:49 CEST 2004
After consultations with the relevant folks, I want to
get 2.4a3 out the door on September 2nd. I'll be following
up to this email with a list of things that are still
pending. This _should_ be the final alpha release. After
that, the first beta.
I'm wondering if there's a way I can mark bugs
and patches that should be in before b1. It appears
from SF's tracker that the only way I'm going to be
able to do that is by putting keywords in the summary.
I'm considering doing this. Rather than rip off the
entirety of the mozilla's insane list of keywords,
here's the ones I care about:
- should be in before b1 (changes functionality)
- should be in before final
- regression since 2.3
Does anyone else have any others that they think are
useful? I'd probably go with something like [beta],
[final], [regr] in the summary. The other alternative
is to make a bunch of new groups - this doesn't excite
me at all, because a) I can't do it, and b) we can't
get rid of them once they're in.
Anthony Baxter <anthony at interlink.com.au>
It's never too late to have a happy childhood.
More information about the Python-Dev