[Python-Dev] Post-2.0 strategy
Fred L. Drake, Jr.
Mon, 16 Oct 2000 15:37:30 -0400 (EDT)
Andrew M. Kuchling writes:
> Then this is a good time to ask what strategy will be followed
> post-2.0. Do you want a moratorium on massive checkins for a time
> while 2.0 shakes out, re-opening the tree for larger changes in a few
> months? Or will you try to live with a CVS branch for 2.0 and re-open
> the tree immediately?
I think a maintenance branch for 2.0.1 (or whatever) should be
created as part of the release process in case we need a quick release
for critical bug fixes.
The tree should be re-opened after the release via a message to
python-dev after the release is published.
Fred L. Drake, Jr. <fdrake at beopen.com>
BeOpen PythonLabs Team Member