RetroSearch Browse

Tue Sep 9 09:16:47 EDT 2003 · https://mail.python.org/pipermail/python-dev/2003-September/037983.html

Barry Warsaw writes:
 > That's a good point.  Release branches are probably overkill for
 > alpha/beta/rc releases, but probably make sense for final releases.  We
 > actually did create one for 2.3, but I screwed up when I named it and
 > that caused a tiny bit of pain in moving to the maintenance branch. 
 > OTOH, for a final release, maybe release branch == maintenance branch.

I think that's sufficient.  There's no need for them to be separate.

  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at acm.org>
PythonLabs at Zope Corporation

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2003-September/037983.html below:

[Pydotorg] Re: [Python-Dev] Documenting branch policy