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

[Brett Cannon]

On Thu, Jul 2, 2009 at 12:01, "Martin v. Löwis" <martin at v.loewis.de> wrote:

> >     The particulars of the revision control system don't matter as much
> >     as the discipline of teaching people to commit fixes. Right now, we
> >     have 2.6.x, 3.0.x and 3.1.x.
> >
> >
> > If I remember correctly I believe we decided at the language summit that
> > 3.0 is just dead now that 3.1 is out and we shouldn't even bother with
> > another point release since 3.1 followed 3.0 so closely and didn't
> > introduce any new syntax or tweak semantics.
>
> Unfortunately, that decision was never communicated to the committers,
> or, for that matter, to people present at the language summit :-(
>

Sorry about that.


>
> So people have continued to merge to 3.0. I think they deserve a 3.0.2
> release.


If Barry is up for it I am not against it, but if we do go with it I think
it should be a quickie release and then retire 3.0.x completely.

-Brett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20090702/c4e3389e/attachment.htm>