[Python-Dev] Python 2.6 and 3.0
barry at python.org
Tue Feb 26 13:28:20 CET 2008
-----BEGIN PGP SIGNED MESSAGE-----
On Feb 25, 2008, at 7:11 PM, Christian Heimes wrote:
> Barry Warsaw wrote:
>> From the follow ups, it sounds like others can pitch in here. A
>> question though: is it reasonable to hold up the monthly release
>> a binary build we're going to make available can't be done at the
>> My preference (at least for the alphas) is "no". If we can make a
>> source release, and if we can build a binary release from exactly the
>> same revision, then we should go ahead and release. I'd rather get
>> alpha out there and in people's hands.
>> We'll almost certainly be stricter for the candidates, finals, and
> I agree. It's not reasonable to hold of alphas because the Windows
> binaries may be released a few days later. Do we need official Windows
> binaries for alphas at all? Martin's buildbot creates nightly Windows
> builds. We could point users to the nightly builds and ask them to
> the version.
That would be find with me. Where are those Windows binaries
available for download from?
>> Dang. I actually don't know how long it's going to take me to do the
>> source release, but I hope it's no more than 3 or 4 hours.
> I guess it's less than 2 hours. You can prepare most of the work like
> the announcements a couple of days earlier. I (perhaps naively) assume
> you have to smack the whip to get everything in place, do the svn cp
> tag, svn export, tar cz, tar xzf && ./configure && make && make test
> dance and upload the tar.gz. Am I missing something important? :]
Dunno yet! It's been years since I did a release and I really want to
check out Anthony's welease tool this time. I may not have time
before Friday to look at this though.
>> When's the PSF gonna start hiring? :)
> Dunno :) But I'm probably the last in a long line of Python core
> developers to get hired. Don't forget I'm still fresh and a junior
> developer. *jk*
>> So, as I mentioned in my last reply, I'm planning to only allow
>> bugs (as described in roundup) hold up the release. Right now
>> there are
>> no critical bugs open.
> #1569 is critical but not important enough to stop an alpha. As I said
> in the other mail it should be fixed for the first beta and must be
> fixed for the first rc.
It's not marked critical in roundup, and that's the only thing I'm
going by! But it doesn't seem critical in the sense that it should
hold up the alpha release, IMO.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
-----END PGP SIGNATURE-----
More information about the Python-Dev