-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Over the next several hours I will be cutting Python 2.6. All lights
and buildbots are go for final release tonight.
I have not yet heard from Trent about press releases, so we'll have to
do those after the fact.
I am also planning on releasing 3.0rc2 tonight, but only if there's
time. Final releases have much more work and the process is much less
tested, so it may take me quite a while to get 2.6 final out.
The trunk and 3.0 branches are officially frozen until further
notice. You /must/ contact me on irc if you need to make any changes.
Remember: #python-dev on irc.freenode.net. Please include my nick
'barry' in any ping so I will notice.
Yee haw!
- -Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSOPRTnEjvBPtnXfVAQIYtAP+JwBnMBLfUqlLbhuy/4QG+nr9fYvDnrp8
/WUHHleUw3uyYsBpxBlJNkmXkA52pPrvLJ7gopUCTuXiWyUZIb+dtczPc/vvZTuV
qw+J1+GRmkMgc/5T5RoEF6rHAUccF7R7llZilsnttBi0TTSrw+fooDJSuqoxqd9k
sMdOlOFMATg=
=HqDw
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
So, we need to come up with a new release schedule for Python 3.0. My
suggestion:
15-Oct-2008 3.0 beta 4
05-Nov-2008 3.0 rc 2
19-Nov-2008 3.0 rc 3
03-Dec-2008 3.0 final
Given what still needs to be done, is this a reasonable schedule? Do
we need two more betas?
- -Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSOqxvnEjvBPtnXfVAQIR5QP/coSi2ltsZSpE2dyUg7Y35QcSk/+4ZbGK
zF0AgLaOkGs+DFnxRH9vy9kN3JaEkp1MhEpDjkomE7kNpnJB7bWotTrHI67HD9ma
ZDqqmaCc02IeUtLm7HuELvofjCgh+gryKWvRc71ErRHmn/YxMGr1OcEirPpx4nZ9
DeDV0OeUtTE=
=RchU
-----END PGP SIGNATURE-----
I received an e-mail from Alex Handy of SD Times:
>Hi there. I read your article on the maturation of Python, and I'm
>looking for contributors to the Python project. I'd love to talk to
>you on the phone for an SD Times article about the subject. I'd also
>appreciate any other members of the project you could refer to
>speaking with.
The subject line of the message was 'Python 3.0', and while I've
replied, I'm not a good person to talk about 3.0 changes or plans.
Does someone want to talk to them about 3.0? Please let me know
privately and I'll pass along Alex's contact info.
--amk
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It was pointed out that the source tarballs I uploaded had some cruft
in them that they shouldn't have, such as svn turds and whatnot.
I've generated new tarballs with that stuff deleted. I do /not/ want
to bump the Python version number for this because this only removes
files that never should have been in the tarball in the first place,
and I cut the new ones from the same r26 tag with no changes.
Would someone please check the new tarballs out and see if they look
right to you:
http://www.python.org/ftp/python/2.6/Python-2.6.tgz.fixedhttp://www.python.org/ftp/python/2.6/Python-2.6.tar.bz2.fixed
Everything unpacks and looks right to me, but I'd love to have another
pair of eyes look at them. If it looks good, I will update the
download page, move the files into place, and send a follow up
announcement to the mailing lists.
Thanks,
- -Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSOUVWXEjvBPtnXfVAQLDbwP+PT3R7MszFgAmFGVerTydvf1ojcpCdnA2
zbPj48GTTSg1jf1f4rzKS19b9/8XkrnJShTD9x0j7oKsqcAAML8quJGZRT9F3rjH
kCEA46TDgrMMpP0hAecAUZPjn/53x8WKqbF7dFTemqY+QThMBZcMGIOAVtqxRCsX
b18X5y+GxIk=
=nn/R
-----END PGP SIGNATURE-----
I propose that the release of 3.0rc2 is deferred until all release
blockers have been resolved (either by actually fixing them, or by
carefully considering that they shouldn't actually block the release).
What else is the point of having the "release blocker" priority, if
they don't actually manage to block the release?
Also, I would like to think that there shouldn't be any
non-documentation changes between the last release candidate, and
the final release(*). Otherwise, what's the point of calling it
a "release candidate" if it doesn't actually get released, later?
IOW, what's the difference to a beta release?
(*) Consequently, there doesn't need to be much more time between
the release candidate and the final release except but a few days,
or, at most, a week.
Regards,
Martin
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Well, I /think/ everything's done, except:
* write and send the announcement
* Martin to upload msi's tomorrow
* fix docs.python.org
Actually, I couldn't figure out what to do to make docs.python.org and
all the other current/dev docs symlinks do the right thing. It's
probably because I'm 1) stupid; 2) completely exhausted; 3) all of the
above. In any case, PEP 101 isn't helpful, so Georg, please fix the
documentation links when you're able. It'd be great if you can take a
pass through PEP 101 and update any documentation related instructions.
Thanks all, this truly was a community release. Huge thanks to my irc-
buds once again.
- -Barry
P.S. The release26-maint branch is now open for 2.6.1. The trunk is
open for 2.7 :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSOQ+6XEjvBPtnXfVAQIMZgP+PQDi1zHkk0pvr2xdAxVXY4QnGCytu4Pp
c+mWmnzVCmtmUsUFMFEeIwruFFdJrCeBiByyYftFW0b95Ru1ld4ajJPJarucmJme
0ocgJk/KdVd0T0xLTxhOKQ3VqDG+6mAwg0lTMu/XdThQsbNCQSm3yK/NiYaY63uq
sPx0keVcSmw=
=tlDv
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Although I'm not quite ready to thaw the tree and make the
announcement, the Python 2.6 final tarballs are now on dinsdale. If
you'd like to grab them and take a look, run the tests, etc, that
would be great.
@dinsdale[/data/ftp.python.org/pub/python/2.6:789]% md5sum Python-2.6*
de4402c1d5465f3960e50ddbbc73cfd7 Python-2.6-docs-html.tar.bz2
5c6f52c3ed321a0a227c1933aa9647f3 Python-2.6-docs-html.tgz
fea8c5c63814ca998e9573fd90e22612 Python-2.6.tar.bz2
2249173d62b455ce30052bec6fe72607 Python-2.6.tgz
http://www.python.org/ftp/python/2.6/Python-2.6-docs-html.tar.bz2http://www.python.org/ftp/python/2.6/Python-2.6-docs-html.tgzhttp://www.python.org/ftp/python/2.6/Python-2.6.tar.bz2http://www.python.org/ftp/python/2.6/Python-2.6.tgz
- -Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSOQBRnEjvBPtnXfVAQIY8QQAmAb0KPBetesunh7WQcMec/KmeVrqD9ne
ca2Q4JA5nKAaD3F9JNsl/2kKuFM/7oXeJlpsYML3S7B3ygYvK6thZIu1ches3Cue
v7Lx+dUk+C4dmYLX/JZvTUbXZmwFSjKucXtt6GhE+U5opcnDDCtaVRbseJTMjq9L
fyXxm4cjHAs=
=Lohi
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've been out of town since Friday, but I don't yet see anything in
the 700 billion email messages I'm now catching up on that leads me to
think we need to delay the release. Yay!
I will be on irc later today and will be trolling through the tracker
and buildbots soon. Don't trust email to get an important issue in
front of me today, please use irc or submit a showstopper bug against
2.6 if something /must/ be addressed before today's release.
I'm going to make a test release at around 1600UTC today, just to see
how building the docs and such go. I'm still planning on doing the
final final release at about 2200UTC. If you need to coordinate with
me (e.g. press releases, Windows builds, etc.) please meeting me on
#python-dev on irc.freenode.net.
- -Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSONrt3EjvBPtnXfVAQJn7wP9HSieFM7daE5vbvsuJGZtHyC2NFmT5Rsm
Fd/ce6CvLzGEkUQ5GQs09TtiZZbIYiObUNkbVQBV8Zbu7A9S3fx7PBpHmPOnIIbr
Dfw39pphdKE76yoJmC7OkFTlDbOw6rbuD+JLAzCgcjxx1MqL1Cx08vl2/WEJf3Fl
izAVTI2Bwwc=
=BCvf
-----END PGP SIGNATURE-----
