[Python-Dev] [Python-3000] 2.6.1 and 3.0 (original) (raw)

Barry Warsaw barry at python.org
Wed Nov 19 16:27:42 CET 2008

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Nov 18, 2008, at 5:17 PM, Martin v. Löwis wrote:

From my point of view bi-monthly release are too much. For a ?.?.1 release two months are fine because several issues are found by 3rd party authors. But after that a release every quarter is sufficient.

* .1 release two months after the .0 release * .2, .3, .4 and .5 release every quarter * about here the next minor release gets out * .6 and further releases after 6 months when necessary In the past, we had been striving for releases every 6 month. This was already very difficult to achieve. While I'm happy that Barry has automated his part to a high degree, my part is, unfortunately, much less automated. I could personally automate the build process a bit more, but part of it is also testing of the installers, which is manual.

Martin, I'm keen on figuring out a way to reduce your workload, and
also to coordinate releases better between us. I /think/ with timed
releases I can tag a little early and give you something to work on so
that the actual release is a matter of fiddling web pages and sending
an announcement.

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin)

iQCVAwUBSSQwbnEjvBPtnXfVAQIOuAP/fxzFpp886TordGNdd4tusqasL/VK2lpr wbhcfwh5TQbVhkhi9CVUFa7BNXCpgxG1nqWT9+ynSdNKIYKnK8kkjRE7FhEYantP TYkuRGI+2DznKjRBtVNXJq+JNktARWKhQwFkc0AmqooCYvhxqt9T5AkEgN4jRn4s YBLaex4g3rA= =Oi0b -----END PGP SIGNATURE-----

More information about the Python-Dev mailing list