Re: [python-committers] state of the 3.2 branch

2011-06-09 Thread R. David Murray
On Wed, 08 Jun 2011 21:29:21 -0700, Ned Deily  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
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers


Re: [python-committers] state of the 3.2 branch

2011-06-09 Thread Georg Brandl
On 06/09/11 17:42, R. David Murray wrote:
> On Wed, 08 Jun 2011 21:29:21 -0700, Ned Deily  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.

Why? All the new stuff is under "new in 3.2.1rc2" which is correct.

Georg

___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers


Re: [python-committers] state of the 3.2 branch

2011-06-09 Thread R. David Murray
On Thu, 09 Jun 2011 19:46:25 +0200, Georg Brandl  wrote:
> On 06/09/11 17:42, R. David Murray wrote:
> > On Wed, 08 Jun 2011 21:29:21 -0700, Ned Deily  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.
> 
> Why? All the new stuff is under "new in 3.2.1rc2" which is correct.

Yeah, but that stuff isn't the kind of stuff you'd normally see
in an RC2.  That's what I meant by weird :).  It's not a big deal.

--
R. David Murray   http://www.bitdance.com
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers