[python-committers] Cutting Python 2.6
Barry Warsaw
barry at python.org
Wed Oct 1 23:48:41 CEST 2008
More information about the python-committers mailing list
Wed Oct 1 23:48:41 CEST 2008
- Previous message: [python-committers] Cutting Python 2.6
- Next message: [python-committers] Cutting Python 2.6
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Oct 1, 2008, at 5:44 PM, Nick Coghlan wrote: > Martin v. Löwis wrote: >> Of course, Anthony is in a different time zone, so when he created >> the tag in his evening, I had all day, and the binaries would still >> be available when he got up the next morning. > > That's a good point - if Barry is on the US west coast somewhere, it > actually works out to about a 17 or 18 hour time advantage for those > of > us in eastern Australia (depending on daylight saving). I'm US/Eastern, but it's not that different. :) > FWIW, I'd personally be fine with the trunk being frozen a day early > if > it was necessary to get the tags and binaries all ready on the day of > release - just so long as it was mentioned in the release PEP. IIUC, the critical bottleneck is tagging the tree, so the RM needs to make it far enough through the PEP to get to that point. Of course that does mean freezing the tree, and I don't think it's too difficult to do that. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSOPwOnEjvBPtnXfVAQJVXQP/YP/JYd7r7KKv1mtZVFBAq9QpTCi6bLse xORM1W42aAYLwRezlmXkVLcoM7ypMk2htH+78VuMtQz6v9GPBkjaMYmwUqrH5SQO cm/mRLouZwX4hgWsATIp9SU+MAUxiKvWisyYWfQKT7uhwakf6nCSLL0Tk6QJXhro K8tIezCxrXw= =K+Ii -----END PGP SIGNATURE-----
- Previous message: [python-committers] Cutting Python 2.6
- Next message: [python-committers] Cutting Python 2.6
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list