[python-committers] Is 3.1 open?
Jesus Cea
jcea at jcea.es
Sun Mar 14 03:14:17 CET 2010
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/14/2010 12:40 AM, Benjamin Peterson wrote:
> 2010/3/13 "Martin v. Löwis" <martin at v.loewis.de>:
>>>>> What about 3.1.3, Benjamin?. I guess it is too late for 3.1.2,
>>>>> since the rc is out. I saw your message asking for stopping commits
>>>>> the 6th march, but I haven't seen another message opening the gates
>>>>> again...
>>>> As Martin pointed out, I don't think this patch is acceptable for a
>>>> bug fix release.
>>>
>>> I would say the patch is acceptable for a bugfix release, just not one
>>> in release candidate status.
>>
>> That's what I meant as well.
>
> Very well then, let's wait for 3.1.3.
That was what I was asking.
I will commit the patch to trunk and py3k, and to 2.6 and 3.1 branch
after 2.6.5 and 3.1.2 are out.
Should I commit now to trunk/py3k and later to 2.6/3.1, or wait to do
the four commits at the same time?. Don't want to miss the 2.7beta.
Mercurial, where are you?. This would be a non issue :)
- --
Jesus Cea Avion _/_/ _/_/_/ _/_/_/
jcea at jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/
jabber / xmpp:jcea at jabber.org _/_/ _/_/ _/_/_/_/_/
. _/_/ _/_/ _/_/ _/_/ _/_/
"Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/
"My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQCVAwUBS5xGeJlgi5GaxT1NAQK24AP+P2w6+11IHzPg9aJk0mmTjonWTBN3Yyqe
o209qKwtKGY5VCs90ttoo/3HyUKWk7T45qjXJ+3yQzLkLmIe0YFkacPQ1zo1RtWS
4mdzp/3uSktpq6/b9ejrmYhyqQzSAqCZJHkMPwaycTfjEUoxwH4V+2E+6zx8zZ58
E9W4vy1zc3k=
=YDlC
-----END PGP SIGNATURE-----
More information about the python-committers
mailing list