[python-committers] state of the 3.2 branch

R. David Murray rdmurray at bitdance.com
Thu Jun 9 17:42:58 CEST 2011


On Wed, 08 Jun 2011 21:29:21 -0700, Ned Deily <nad at acm.org> wrote:
> 
> On Jun 8, 2011, at 18:43 , R. David Murray wrote:
> 
> > I am completely confused by the state of the 3.2 branch.  My understanding
> > is that RC1 has been released, that RC2 is coming soon, and that Georg
> > is releasing 3.2.1 from a separate clone so that we do not have to have
> > a freeze in the main repo.  All that is fine, but the main repo NEWS
> > file is headed by "What's New in Python 3.2.1 Release candidate 2?",
> > yet there are clearly news items in that section that should not be
> > going in to release candidate 2.  As an arbitrary example, take:
> > 
> >    - Issue #12175: FileIO.readall() now raises a ValueError instead of
> >      an IOError if the file is closed.
> > 
> > That seems to me to be clearly not a critical fix, and thus not
> > appropriate for the RC stage.
> 
> Georg announced earlier that rc1 is dead so anything is allowed into rc2:
> 
> http://permalink.gmane.org/gmane.comp.python.committers/1677

Ah, thank you.  I must have misunderstood that when I read it the first
time (I do have a vague memory of reading it).  I will just translate
"rc2" to "rc1" in my head and solder on :)

I still does make the NEWS history look weird, though.

--
R. David Murray           http://www.bitdance.com


More information about the python-committers mailing list