Request: new zc.buildout release
Could we have a new release of zc.buildout please? 1.5.2 was released nearly 2 years ago, and trunk now contains some interesting bug fixes and new features. If there is something blocking a 1.6 release, could we see about branching off the 1.5.x line to at least push out the bug fixes? -- Martijn Pieters www.zopatista.com
On Thu, Jul 12, 2012 at 7:07 AM, Martijn Pieters <mj@zopatista.com> wrote:
Could we have a new release of zc.buildout please? 1.5.2 was released nearly 2 years ago, and trunk now contains some interesting bug fixes and new features.
If there is something blocking a 1.6 release,
Other than time, no.
could we see about branching off the 1.5.x line to at least push out the bug fixes?
If someone wants to work on either, that's cool. I think 1.6 would be easier. I'm working on buildout 2: https://github.com/buildout/buildout (I've gotten blocked a bit dealing with Python 3.3. I should probably set that aside and get 2a3 out sooner.) And don't have time for buildout 1. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm
On Jul 12, 2012, at 15:40 , Jim Fulton wrote:
I'm working on buildout 2:
https://github.com/buildout/buildout
(I've gotten blocked a bit dealing with Python 3.3. I should probably set that aside and get 2a3 out sooner.)
Ah, I merged a fix I made on trunk into the svn '2' branch, but I now guess that it won't make it to your git repository. Perhaps the '2' branch should be nixed from SVN and replaced with a 'moved to github' sign?
And don't have time for buildout 1.
Can we just release it as is then? Who with access on pypi can do this? -- Martijn Pieters www.zopatista.com
On Thu, Jul 12, 2012 at 9:51 AM, Martijn Pieters <mj@zopatista.com> wrote:
On Jul 12, 2012, at 15:40 , Jim Fulton wrote:
I'm working on buildout 2:
https://github.com/buildout/buildout
(I've gotten blocked a bit dealing with Python 3.3. I should probably set that aside and get 2a3 out sooner.)
Ah, I merged a fix I made on trunk into the svn '2' branch, but I now guess that it won't make it to your git repository. Perhaps the '2' branch should be nixed from SVN and replaced with a 'moved to github' sign?
Perhaps.
And don't have time for buildout 1.
Can we just release it as is then? Who with access on pypi can do this?
Well, "just" releasing it means testing it on at least windows, mac and ubuntu. Fixing any (non-intermittent) test failures and releasing. If someone is willing to do all of that (dealing with the hassle of setting up a dev environment with clean Python's), then I'll authorize them to make a release. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm
On 7/12/12 7:07 AM, Martijn Pieters wrote:
Could we have a new release of zc.buildout please? 1.5.2 was released nearly 2 years ago, and trunk now contains some interesting bug fixes and new features.
Such as? Just curious…
If there is something blocking a 1.6 release, could we see about branching off the 1.5.x line to at least push out the bug fixes?
-- Martijn Pieters www.zopatista.com <http://www.zopatista.com>
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
-- Alex Clark · http://pythonpackages.com/ONE_CLICK_RELEASE
On Thu, Jul 12, 2012 at 3:59 PM, Alex Clark <aclark@aclark.net> wrote:
On 7/12/12 7:07 AM, Martijn Pieters wrote:
Could we have a new release of zc.buildout please? 1.5.2 was released nearly 2 years ago, and trunk now contains some interesting bug fixes and new features.
Such as? Just curious…
See the changes for 1.6: http://svn.zope.org/zc.buildout/trunk/CHANGES.txt?view=auto Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm
participants (3)
-
Alex Clark
-
Jim Fulton
-
Martijn Pieters