[python-committers] Why r69846 is not merged to"release26-maint"?

[Steve Holden]

Raymond Hettinger wrote:
> 
>> So people have continued to merge to 3.0. I think they deserve a 3.0.2
> release.
> 
> I'm one of those people who have backported fixes to 3.0, but I do not want
> a 3.0.2 to go out now thet 3.1 has been released.  The latest version should
> not get upstaged.  Essentially, 3.1 is what 3.0.x should have been.  The
> 3.0.x series
> is defective and needs to die-off and be forgotten.
>  
> So, not only would 3.0.2 be a waste of Barry's time, it would be a step
> backwards.
> A while ago, Barry said that 3.0.2 would not happen, so at that point
> several of
> us stopped backporting fixes.  So, 3.0.2 still has known bugs and I
> think it would
> be a mistake to release it.
>  
>  

Suggested text for press release:

"""
3.0 is dead. It is pushing up the daisies. It has ceased to be. It is no
more. It has joined the choir invisible. It is an ex-release.
"""

regards
 Steve
-- 
Steve Holden           +1 571 484 6266   +1 800 494 3119
Holden Web LLC                 http://www.holdenweb.com/
Watch PyCon on video now!          http://pycon.blip.tv/