[Python-3000] The release process

[Barry Warsaw]

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

On Mar 1, 2008, at 3:04 PM, Christian Heimes wrote:

> I *never* sync changes from trunk Misc/NEWS to py3k Misc/NEWS. From my
> point of view it doesn't make sense to put Python 2.6 changes in the
> same section as Python 3.0 changes. Moving changes from to the right
> section would put a large and unnecessary burden on me. In general  
> every
> change of the 2.6 source tree makes it into 3.0. Exceptions to the  
> rule
> is stuff that makes no sense like 3.0 compatibility and warnings.
>
> Thumb rule: Changes, bug fixes and new features in 2.6 are also in 3.0
> except they are outruled by a Python 3.0 feature.
>
> Several people including me and Guido himself are watching the cvs
> lists. We make sure everybody adds an entry to Misc/NEWS whenever a  
> bug
> is fixed or a new feature is added. Otherwise we crack the whip ^H^H^H
> contact the committer. You can be sure that at least 98% of  all  
> closed
> bug reports, feature request and important changes have an entry in
> Misc/NEWS.

Great, this is all I'm really asking for!  The point of my  
unconscionable rant :) was that I think it's unfeasible to update the  
NEWS files at release time.  Knowing that you, Guido and others are  
keeping an eye on commits and an iron hand on the NEWS files makes me  
as the RM rest comfortably. :)

> So in general Misc/NEWS isn't an issue but Docs/whatsnew/ is. Only a
> couple of people - mostly Georg and Andrew - are updating the files.

I think it's okay if these lag behind during the alphas, but it would  
be good to start whipping these in shape by the time we start  
releasing betas.

Thanks,
- -Barry

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

iQCVAwUBR8ncx3EjvBPtnXfVAQJeNQP+L2wK4CmGfwzgsQUHQISniaJ2rREBhJua
sJwqGNpBhnf6Uc8jJz+JRiexPdCW4AlH34FtHkyRkw2ZIVWwd6sO+7ixQPk0A/TP
+gGk1uST/sjPG3q8T5u9OElri5SoTqJzEgWMkTiGhwYouSvOjpW/GFFREySU68Tk
h9XGzJFZex0=
=aXqC
-----END PGP SIGNATURE-----