[python-committers] Cutting Python 2.6
Barry Warsaw
barry at python.org
Fri Oct 3 14:09:06 CEST 2008
More information about the python-committers mailing list
Fri Oct 3 14:09:06 CEST 2008
- Previous message: [python-committers] Cutting Python 2.6
- Next message: [python-committers] Cutting Python 2.6
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Oct 3, 2008, at 12:34 AM, Anthony Baxter wrote: > It's happened a couple of times when I've made releases - the process > I had was to automate it as much as possible, then take the generated > tarball, unpack it freshly and run the full tests, and then check > things like the README and all those other places. Making a release is > still a pretty fiddly process, and things slip through. Anthony's spot on. Even with a release script and PEP 101, it's still pretty labor intensive. Of course, Python 2.7 and 3.1 still have no official RM <wink> so if you want firsthand experience, the opportunity is available. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSOYLY3EjvBPtnXfVAQLR1QP6A4rhYAPQ1BJwRsHPcg9aBB7jKYD7I77f T2C0+rn3303mI8zwF/iVQ+0QX7EM5MYzIniu1IReZxh+9jgZ5abyPSj3oqedpeaO XKBKzT8v5TN1G6LvdgyiUESQGE29UPSIRdMzRRurdKN0tlMZOBLYr4/nf128cNFL cLqg02NHmr4= =iLa3 -----END PGP SIGNATURE-----
- Previous message: [python-committers] Cutting Python 2.6
- Next message: [python-committers] Cutting Python 2.6
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list