[python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)
Jesus Cea
jcea at jcea.es
Tue May 12 20:18:26 CEST 2015
Larry, could you comment about the impact in the buildbots?. I suppose
option #1 could allows us to test both 3.5 and 3.6 changes. Would you
confirm this?
My votes:
Workflow #0: -0
Workflow #1: +1
Workflow #2: +0
Would be great if we could host the branch for 3.5 ourselves instead of
using BitBucket but, at least, it is NOT github :). Competition is good.
--
Jesús Cea Avión _/_/ _/_/_/ _/_/_/
jcea at jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/
Twitter: @jcea _/_/ _/_/ _/_/_/_/_/
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/python-committers/attachments/20150512/0586ae8c/attachment.sig>
More information about the python-committers
mailing list