-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Python 3.3 is currently in beta, so the rythm of new patches in "default" will decrease and people with new features MUST wait until 3.3 is out. I think this is a waste of time. And even if people is working with HG private clones, they can't test using the buildbots neither mark a bug as fixed in the tracker.
If we create a new 3.3 branch *NOW* and add it to the buildbots, people can keep working in "default" full speed (for 3.4), while 3.3 branch is getting ready for general release. We only need to remember to appy the same rule current rule: any patch in branch "x" must be "merged" into branch "x+1" too.
Has this step been considered?. I think it is a nice improvement that HG enables and we are not using.
What do you think?.
PS: In the past some people said that this "feature freeze" forces devs to concentrate in getting the release ready. This is a good point, but it should be a social issue to solve, not a technical one. I, for one, would personally invest more time in fixing upcoming 3.3 (soon to be released) than hacking future 3.4 (two years away!). No need to "press me" with an ¿obsolete? technical limitation.
Jesus Cea Avion _/_/ _/_/_/ _/_/_/ jcea@jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ jabber / xmpp:jcea@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.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQCVAwUBT+z1cJlgi5GaxT1NAQLt0AP8DsFzMms7Z5JhomDZaTZkZB2X5Dh7SBkK 0XwM5oKASIa2k9OEX8CbKJI6u6dCUT3VGS3qbXNcv1baoK8ldykt2Ats9XHXL3gD 9ZX4Ofcm6Qw738s9OgvsQnDFYcx9FtB8wew5b6qnAsRtDWEo5iv88ZzZEtNMNbxW Rcv9exP38JY= =N8z9 -----END PGP SIGNATURE-----