[Python-Dev] 2.3.6 for the unicode buffer overrun

[Barry Warsaw]

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

On Oct 12, 2006, at 5:03 PM, Gregory P. Smith wrote:

> IMHO thats a backwards view; I'm with Barry.  Requiring human
> intervention to do anything other than press the big green "go" button
> to launch the "official" release build process is an opportunity for
> human error.  the same goes for testing the built release installers
> and tarballs.

Oh yes, that's an important step I forgot to mention.  At work, we  
also run automated tests of the built installers, so we have a high  
degree of confidence that what our buildbot farm produces at least  
passes the sniff test (/then/ our QA dept takes over from there).   
The files we upload then are named by product, platform, version,  
revision id, and date.  It takes a manual step to delete old builds,  
but we have big disks so we generally don't do that except for EOL'd  
versions.  The nice thing about that is that you can go back to  
almost any build and pull down a working installer.

Greg hints at a major benefit of this: the knowledge for how to  
successfully build products is contained in scripts that are  
themselves revision controlled.  A wiki page providing an overview  
and the starting points are still needed but rarely consulted.

> i'm not volunteering to setup an automated system for this but i've
> got good ideas how to do it if i ever find time or someone wants to
> chat offline. :(

I wish I had the cycles to volunteer to help out implementing this. :(

- -Barry

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

iQCVAwUBRS608nEjvBPtnXfVAQIypAQAtiantWJkvStPYR8tnl+AU+HzI7bZ54s1
oX8Ni0/1IbZQwYloV6UMmhwisirZ5bwAtNWfZnd3UQXFhrCC1MGlRMOWP/y6AwS2
/gSzUV9A1dxUE9iVdPy50gEMFrzrZ32g16+FsHzae/9FgklB+GjogAuYmr2vbxd4
SrB1dgEHnXg=
=6rIv
-----END PGP SIGNATURE-----