[Python-Dev] TRUNK UNFROZEN (release is done)

Michael Hudson mwh at python.net
Tue Oct 26 13:34:30 CEST 2004

Jim Fulton <jim at zope.com> writes:

> Anthony Baxter wrote:
>> The first beta is out, so the trunk is unfrozen, and available for
>> checkins.
>> Now that we're in beta, we shouldn't see any new features or
>> behaviour
>> changing fixes going into the trunk, unless it's been seen and agreed
>> to on python-dev.
> Why not create a release branch?  That would free up the trunk for new work
> and reduce the chance of new features creeping in.
> I realize this is discussed briefly in PEP 101, but that PEP doesn't
> give a rational for waiting until the final release to make a release branch.
> It makes more sense to me to make the branch when features are frozen,
> which means the beta.

Didn't this get tried before?  Are you volunteering to port all the
various bugfixy type things from whichever branch they get committed
on to the other?  I'm sure as hell not.


  We did requirements and task analysis, iterative design, and user
  testing. You'd almost think programming languages were an interface
  between people and computers.                    -- Steven Pemberton
          (one of the designers of Python's direct ancestor ABC)

More information about the Python-Dev mailing list