GeezerVison

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

On May 9, 2008, at 8:15 AM, skip at pobox.com wrote:

> In the past I seem to recall that the Python code proper might be  
> frozen
> (for a day or two) before a release, but that it was okay to still  
> commit
> changes to non-code files such as documentation or files in Misc.   
> Is this
> still the case in the new release-early-release-often regime?  Is the
> intention to make the duration of the code freeze so short (a few  
> minutes or
> hours) that it's not worth the effort to make this distinction?

For the alphas, that's certainly been the case because it hasn't been  
necessary to coordinate all the Experts.  IOW, it's okay for the  
Windows installer to get uploaded a few hours after the tarballs.

For the betas, rcs and finals, I think we want a little bit more  
coordination (correct me if you disagree).  So in that case, there may  
be a longer freeze.  Even in that case, I don't envision more than a  
24 hour freeze hopefully.

- -Barry

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

iQCVAwUBSCRR5HEjvBPtnXfVAQLa+gP8CL9koa5eGBvP8g+CA8l61SIuluHNbPkq
SH7uOiPMeuIX392xy82ixnXjYTlCJn9epWouYkiWta3GA+ZaCcmTFFavZ3ZbLbE3
uxfzhCWsZ5EUW5/iDCOUrlEwuxXJ6FU4naRTaTCBTELXRKvb3sI5C2pFjrb6JTZc
hP2hP6m+A2Y=
=avCD
-----END PGP SIGNATURE-----