Vacation; Python 2.2.3 release.
I'm going on vacation tomorrow; I'll be in Holland for 10 days and will return to the US on May 26. I expect to have some email access but won't use it much. Now, I'd like Python 2.2.3 to be released soon. Barry has volunteered to be the release manager. I think it's pretty much ready to go out any time, except that Jeremy mentioned that he has a few things he'd like to backport; since Jeremy and Barry share an office I'm sure they can work this out. :-) I won't be disappointed if 2.2.3 hasn't been released yet when I'm back, but I won't be surprised if in fact it does go out while I'm gone -- it's ready, stick a fork in it! :-) --Guido van Rossum (home page: http://www.python.org/~guido/)
On Thu, 2003-05-15 at 17:32, Guido van Rossum wrote:
Now, I'd like Python 2.2.3 to be released soon. Barry has volunteered to be the release manager.
Stupid question. Where can I get a prerelease (or CVS access) to 2.2.3, or a list of patches/features applied since 2.2.2? I looked around for the info, but apparently not hard enough (or I just don't understand CVS branching well enough). Chad
[Chad Netzer]
Stupid question. Where can I get a prerelease (or CVS access) to 2.2.3, or a list of patches/features applied since 2.2.2? I looked around for the info, but apparently not hard enough (or I just don't understand CVS branching well enough).
It's not a stupid question, it's a maddening feature of CVS that there's no place to store meta-data about branches. What you want to do is pass this argument to the checkout command: -r release22-maint There's no reasonable way you could have guess that. The Misc/NEWS file in that branch summarizes the changes since 2.2.2 (at least those fixes that people bothered to make a NEWS entry for <winK>).
Guido van Rossum wrote Now, I'd like Python 2.2.3 to be released soon. Barry has volunteered to be the release manager. I think it's pretty much ready to go out any time, except that Jeremy mentioned that he has a few things he'd like to backport; since Jeremy and Barry share an office I'm sure they can work this out. :-)
There's a bunch of cvs commit messages I've saved off as "potential
branch-patches". I might try to get to them this weekend.
--
Anthony Baxter
Anthony Baxter
Guido van Rossum wrote Now, I'd like Python 2.2.3 to be released soon. Barry has volunteered to be the release manager. I think it's pretty much ready to go out any time, except that Jeremy mentioned that he has a few things he'd like to backport; since Jeremy and Barry share an office I'm sure they can work this out. :-)
There's a bunch of cvs commit messages I've saved off as "potential branch-patches". I might try to get to them this weekend.
My python-bugfixes mbox is still online: http://starship.python.net/crew/mwh/python-bugfixes Some of it might still be relavent -- I haven't been that conscientious about keeping it up to date. Cheers, M. -- The PROPER way to handle HTML postings is to cancel the article, then hire a hitman to kill the poster, his wife and kids, and fuck his dog and smash his computer into little bits. Anything more is just extremism. -- Paul Tomblin, asr
On Fri, 2003-05-16 at 06:47, Michael Hudson wrote:
There's a bunch of cvs commit messages I've saved off as "potential branch-patches". I might try to get to them this weekend.
My python-bugfixes mbox is still online:
http://starship.python.net/crew/mwh/python-bugfixes
Some of it might still be relavent -- I haven't been that conscientious about keeping it up to date.
I definitely do not have the time to triage or apply backports. I think you'll have to use your own judgment, tempered by your available time, to decide which patches should be backported. Guido obviously thinks 2.2.3 is ready now so you should prioritize, but be conservative. If you have specific questions, python-dev is the place to ask. -Barry
On Thu, 2003-05-15 at 20:32, Guido van Rossum wrote:
I'm going on vacation tomorrow; I'll be in Holland for 10 days and will return to the US on May 26. I expect to have some email access but won't use it much.
Now, I'd like Python 2.2.3 to be released soon. Barry has volunteered to be the release manager. I think it's pretty much ready to go out any time, except that Jeremy mentioned that he has a few things he'd like to backport; since Jeremy and Barry share an office I'm sure they can work this out. :-)
I won't be disappointed if 2.2.3 hasn't been released yet when I'm back, but I won't be surprised if in fact it does go out while I'm gone -- it's ready, stick a fork in it! :-)
FWIW, I'm going to be around, and am fairly free during the US Memorial Day weekend 24th - 26th. Can we shoot for getting a release out that weekend? If we can code freeze by the 22nd, I can throw together a release candidate on Friday (with Tim's help for Windows) and a final by Monday. What do you folks think? -Barry
Barry Warsaw writes:
FWIW, I'm going to be around, and am fairly free during the US Memorial Day weekend 24th - 26th. Can we shoot for getting a release out that weekend? If we can code freeze by the 22nd, I can throw together a release candidate on Friday (with Tim's help for Windows) and a final by Monday.
I'll be away that Friday through Tuesday, and don't expect any kind of internet/email access. -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Zope Corporation
On Thu, 2003-05-15 at 22:30, Fred L. Drake, Jr. wrote:
Barry Warsaw writes:
FWIW, I'm going to be around, and am fairly free during the US Memorial Day weekend 24th - 26th. Can we shoot for getting a release out that weekend? If we can code freeze by the 22nd, I can throw together a release candidate on Friday (with Tim's help for Windows) and a final by Monday.
I'll be away that Friday through Tuesday, and don't expect any kind of internet/email access.
So can we have all the doc changes in place before then, or should we freeze on Wednesday? -Barry
Barry Warsaw writes:
So can we have all the doc changes in place before then, or should we freeze on Wednesday?
We can probably have things done; there's only one big thing that needs to be back-ported in the docs. (I'm pretty sure we solved a fonts problem on the trunk; that fix really needs to be back-ported, but I'll have to spend a little time digging it out. This is really reason to separate the documentation processing tools from the doc tree.) Normally, the docs distributed with a release candidate are marked as being for the RC in the versioning; I could build both sets of packages ahead of time if we get the CVS tagging right. That would prevent any changes to the docs after the RC, which should be fine. We can deal with the mechanics of that next week, to the extent that anything much needs to happen. -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Zope Corporation
Barry Warsaw writes:
FWIW, I'm going to be around, and am fairly free during the US Memorial Day weekend 24th - 26th. Can we shoot for getting a release out that weekend? If we can code freeze by the 22nd, I can throw together a release candidate on Friday (with Tim's help for Windows) and a final by Monday.
I'd like to see the following patches included, they are in HEAD and currently applied in the python2.2 Debian packages, so they got some testing. - Send anonymous password when using anonftp Lib/ftplib.py 1.62 1.63 See http://python.org/sf/497420 - robotparser.py fails on some URLs (including change of copyright from "Python 2.0 open source license"). See http://python.org/sf/499513 - make tkinter compatible with tk-8.4.2. See http://python.org/sf/707701 Matthias
On Mon, 2003-05-19 at 14:13, Matthias Klose wrote:
I'd like to see the following patches included, they are in HEAD and currently applied in the python2.2 Debian packages, so they got some testing.
- make tkinter compatible with tk-8.4.2. See http://python.org/sf/707701
Don't know about the others, but this one at least seems to have been applied. Chad
Matthias Klose writes:
Barry Warsaw writes:
FWIW, I'm going to be around, and am fairly free during the US Memorial Day weekend 24th - 26th. Can we shoot for getting a release out that weekend? If we can code freeze by the 22nd, I can throw together a release candidate on Friday (with Tim's help for Windows) and a final by Monday.
I'd like to see the following patches included, they are in HEAD and currently applied in the python2.2 Debian packages, so they got some testing.
- make tkinter compatible with tk-8.4.2. See http://python.org/sf/707701
oops, sorry this one is already applied.
Matthias Klose wrote:
- make tkinter compatible with tk-8.4.2. See http://python.org/sf/707701
As the comment indicates, the patch was already applied as 1.160.10.3. Is anything needed beyond that?
- Send anonymous password when using anonftp Lib/ftplib.py 1.62 1.63 See http://python.org/sf/497420
- robotparser.py fails on some URLs (including change of copyright from "Python 2.0 open source license"). See http://python.org/sf/499513
I will look into those two. Regards, Martin
I seem to remember that there's one or two bugfixes assigned to me that
I thought
fairly important for 2.2.3 at the time. Unfortunately sf.net is down at
the moment, so I can't check this, and I don't remember whether they
were OSX-related (so they
have to go into the main release) or OS9 only (so they needn't hold up
the main
release).
I'll try to get around to these tomorrow.
--
Jack Jansen,
participants (10)
-
"Martin v. Löwis" -
Anthony Baxter -
Barry Warsaw -
Chad Netzer -
Fred L. Drake, Jr. -
Guido van Rossum -
Jack Jansen -
Matthias Klose -
Michael Hudson -
Tim Peters