Home Original page

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

Brett Cannon brett at python.org
Fri Jul 3 00:23:57 CEST 2009 
On Thu, Jul 2, 2009 at 15:21, Raymond Hettinger <python at rcn.com> 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.
>

Sounds like general consensus that 3.0.2 isn't worth it. Is an announcement
on c.l.p.a and something on www.python.org enough to get the word out that
3.0.2 is not going to happen and 3.0 users should migrate to 3.1?

-Brett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20090702/3d5812b8/attachment.htm>
More information about the python-committers mailing list