-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 29/09/12 10:35, Georg Brandl wrote:
> Until the last ordinary 3.2 bugfix release is done (which will be
> soon), the usual procedure for 3.x will be to check into 3.2, merge
> into 3.3, and then merge into default, except of course for a)
> fixes of 3.3-only features and b) trivial things like typos that
> you don't feel have to be in 3.2.4.
>
> default is now Python 3.4, and new features can be committed
> there.
So, if I understand correctly, the current situation is this:
2.6: Security fixes only
2.7, 3.2, 3.3: Bugfixes only
2.3, 2.4, 2.5, 3.0, 3.1: Dead
After 3.2.4 is published ("soon"), 3.2 would move to "security fixes
only". Am I right?
I wonder if we have a deadline for supporting 2.6 yet. How about 2.7?.
- --
Jesús Cea Avión _/_/ _/_/_/ _/_/_/
j...@jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/
jabber / xmpp:j...@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://www.enigmail.net/
iQCVAwUBUGkACplgi5GaxT1NAQKKCgP/Te1AZgjtr2YAg3fq5NmtOZhkL5KYfodt
xhFpTShdC7ELc/PpdAI67UdnpwL0PoceKpQ65Bidei/EUG9oJAuHiKdaCDPBzGDN
Z6r9eRwozMia8rT/7w2WiGH88LWHloimErQsLjeJTmymKOViRHjEeMOeYmyYclJd
LzGQJaEW20M=
=eX2O
-----END PGP SIGNATURE-----
_______________________________________________
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers
