The long anticipated "emergency" 2.7.5 release has now been tagged. It will be publicly announced as binaries arrive. Originally, I was just going to cherrypick regression fixes onto the 2.7.4 release and release those as 2.7.5. I started to this but ran into some conflicts. Since we don't have buildbot testing of release branches, I decided it would be best to just cut from the maintenance branch. -- Regards, Benjamin
Am 12.05.2013 06:03, schrieb Benjamin Peterson:
The long anticipated "emergency" 2.7.5 release has now been tagged. It will be publicly announced as binaries arrive.
Originally, I was just going to cherrypick regression fixes onto the 2.7.4 release and release those as 2.7.5. I started to this but ran into some conflicts. Since we don't have buildbot testing of release branches, I decided it would be best to just cut from the maintenance branch.
3.2.5 and 3.3.2 are coming along as well. Georg
On Sun, 12 May 2013 13:24:45 +0200 Georg Brandl <g.brandl@gmx.net> wrote:
Am 12.05.2013 06:03, schrieb Benjamin Peterson:
The long anticipated "emergency" 2.7.5 release has now been tagged. It will be publicly announced as binaries arrive.
Originally, I was just going to cherrypick regression fixes onto the 2.7.4 release and release those as 2.7.5. I started to this but ran into some conflicts. Since we don't have buildbot testing of release branches, I decided it would be best to just cut from the maintenance branch.
3.2.5 and 3.3.2 are coming along as well.
3.3.2 can't be released before http://bugs.python.org/issue17962 is fixed. Regards Antoine.
On 12.05.2013 06:03, Benjamin Peterson wrote:
The long anticipated "emergency" 2.7.5 release has now been tagged. It will be publicly announced as binaries arrive.
Originally, I was just going to cherrypick regression fixes onto the 2.7.4 release and release those as 2.7.5. I started to this but ran into some conflicts. Since we don't have buildbot testing of release branches, I decided it would be best to just cut from the maintenance branch.
Has the release been postponed ? I don't see it on http://www.python.org/download/ Incidentally, the schedule already lists 2.7.5 as released on 2013-05-12 (http://www.python.org/dev/peps/pep-0373/) and the release calendar on 2013-05-11: https://www.google.com/calendar/feeds/b6v58qvojllt0i6ql654r1vh00@group.calendar.google.com/public/basic?orderby=starttime&sortorder=descending :-) -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, May 15 2013)
Python Projects, Consulting and Support ... http://www.egenix.com/ mxODBC.Zope/Plone.Database.Adapter ... http://zope.egenix.com/ mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
2013-05-07: Released mxODBC Zope DA 2.1.2 ... http://egenix.com/go46 2013-05-06: Released mxODBC 3.2.3 ... http://egenix.com/go45 ::::: Try our mxODBC.Connect Python Database Interface for free ! :::::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/
2013/5/15 M.-A. Lemburg <mal@egenix.com>:
On 12.05.2013 06:03, Benjamin Peterson wrote:
The long anticipated "emergency" 2.7.5 release has now been tagged. It will be publicly announced as binaries arrive.
Originally, I was just going to cherrypick regression fixes onto the 2.7.4 release and release those as 2.7.5. I started to this but ran into some conflicts. Since we don't have buildbot testing of release branches, I decided it would be best to just cut from the maintenance branch.
Has the release been postponed ?
I don't see it on http://www.python.org/download/
We're waiting for binaries.
Incidentally, the schedule already lists 2.7.5 as released on 2013-05-12 (http://www.python.org/dev/peps/pep-0373/) and the release calendar on 2013-05-11: https://www.google.com/calendar/feeds/b6v58qvojllt0i6ql654r1vh00@group.calendar.google.com/public/basic?orderby=starttime&sortorder=descending :-)
In practice, those dates mean when I tag the release. -- Regards, Benjamin
On 15.05.2013 19:11, Benjamin Peterson wrote:
2013/5/15 M.-A. Lemburg <mal@egenix.com>:
On 12.05.2013 06:03, Benjamin Peterson wrote:
The long anticipated "emergency" 2.7.5 release has now been tagged. It will be publicly announced as binaries arrive.
Originally, I was just going to cherrypick regression fixes onto the 2.7.4 release and release those as 2.7.5. I started to this but ran into some conflicts. Since we don't have buildbot testing of release branches, I decided it would be best to just cut from the maintenance branch.
Has the release been postponed ?
I don't see it on http://www.python.org/download/
We're waiting for binaries.
Ah, ok. Thanks for the heads-up.
Incidentally, the schedule already lists 2.7.5 as released on 2013-05-12 (http://www.python.org/dev/peps/pep-0373/) and the release calendar on 2013-05-11: https://www.google.com/calendar/feeds/b6v58qvojllt0i6ql654r1vh00@group.calendar.google.com/public/basic?orderby=starttime&sortorder=descending :-)
In practice, those dates mean when I tag the release.
Ok. Was just wondering whether something went wrong with the website. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, May 15 2013)
Python Projects, Consulting and Support ... http://www.egenix.com/ mxODBC.Zope/Plone.Database.Adapter ... http://zope.egenix.com/ mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
2013-05-07: Released mxODBC Zope DA 2.1.2 ... http://egenix.com/go46 2013-05-06: Released mxODBC 3.2.3 ... http://egenix.com/go45 ::::: Try our mxODBC.Connect Python Database Interface for free ! :::::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/
Am 15.05.2013 09:55, schrieb M.-A. Lemburg:
On 12.05.2013 06:03, Benjamin Peterson wrote:
The long anticipated "emergency" 2.7.5 release has now been tagged. It will be publicly announced as binaries arrive.
Originally, I was just going to cherrypick regression fixes onto the 2.7.4 release and release those as 2.7.5. I started to this but ran into some conflicts. Since we don't have buildbot testing of release branches, I decided it would be best to just cut from the maintenance branch.
Has the release been postponed ?
I don't see it on http://www.python.org/download/
Incidentally, the schedule already lists 2.7.5 as released on 2013-05-12 (http://www.python.org/dev/peps/pep-0373/) and the release calendar on 2013-05-11: https://www.google.com/calendar/feeds/b6v58qvojllt0i6ql654r1vh00@group.calendar.google.com/public/basic?orderby=starttime&sortorder=descending :-)
We're still waiting for the Windows binaries. I think I will publish the source and Mac releases on the website now and make a note that Windows is coming shortly. Has anybody heard from Martin recently? I hope he's well and just overworked... Georg
On Wed, May 15, 2013 at 1:07 PM, Georg Brandl <g.brandl@gmx.net> wrote:
Am 15.05.2013 09:55, schrieb M.-A. Lemburg:
On 12.05.2013 06:03, Benjamin Peterson wrote:
The long anticipated "emergency" 2.7.5 release has now been tagged. It will be publicly announced as binaries arrive.
Originally, I was just going to cherrypick regression fixes onto the 2.7.4 release and release those as 2.7.5. I started to this but ran into some conflicts. Since we don't have buildbot testing of release branches, I decided it would be best to just cut from the maintenance branch.
Has the release been postponed ?
I don't see it on http://www.python.org/download/
Incidentally, the schedule already lists 2.7.5 as released on 2013-05-12 (http://www.python.org/dev/peps/pep-0373/) and the release calendar on 2013-05-11: https://www.google.com/calendar/feeds/b6v58qvojllt0i6ql654r1vh00@group.calendar.google.com/public/basic?orderby=starttime&sortorder=descending :-)
We're still waiting for the Windows binaries.
I think I will publish the source and Mac releases on the website now and make a note that Windows is coming shortly.
I'm going to get started building the MSIs this evening. I'm looking into how I can obtain a code signing certificate, otherwise we'd potentially be shipping unsigned security releases...*ducks*
Has anybody heard from Martin recently? I hope he's well and just overworked...
I asked some folks on the infrastructure team and the last they heard from him was 11 April.
participants (7)
-
"Martin v. Löwis" -
Antoine Pitrou -
Benjamin Peterson -
Brian Curtin -
Georg Brandl -
M.-A. Lemburg -
Zachary Ware