hello,
On 13/06/2010 Hanno Schlichting wrote:
On Sat, Jun 12, 2010 at 10:45 PM, Jonas Meurer jo...@freesources.org wrote:
another build system would be magnificent :-)
the new build system in zope2.12 makes it hard/impossible to distribute
zope2 binaries within linux/*bsd/hurd/...
Hi.
On Mon, Jun 14, 2010 at 4:16 PM, Jonas Meurer jo...@freesources.org wrote:
first, thanks for clarifying. did i get you right, that for the future,
monolithic source releases of zope2 are planned again once the dust has
settled?
No. There is currently no monolithic released planned at all.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jonas Meurer wrote:
hello,
On 13/06/2010 Hanno Schlichting wrote:
On Sat, Jun 12, 2010 at 10:45 PM, Jonas Meurer jo...@freesources.org wrote:
another build system would be magnificent :-)
the new build system in zope2.12 makes it
Hi there,
thanks to all of you for the feedback. Given the general agreement to
the plan, I'm going to release a first alpha on Friday June 25.
More alpha releases will follow depending on the changes that go into
the codebase. But I expect them on a roughly 3-4 weeks basis. If the
code stays as
Am 12.06.2010, 20:58 Uhr, schrieb Hanno Schlichting ha...@hannosch.eu:
Comments, suggestions, more work you'd like to get into 2.13?
Hi Hanno,
thanks for the information. I'm a little confused by the narrative - is
Plone 4.0 being held back by a Zope 2 release? As I don't use Plone I
don't
Hi Charlie,
On Sun, Jun 13, 2010 at 2:06 PM, Charlie Clark
charlie.cl...@clark-consulting.eu wrote:
thanks for the information. I'm a little confused by the narrative - is
Plone 4.0 being held back by a Zope 2 release?
No, Plone 4 is delayed for all the normal reasons of too many open
bugs
On Sat, Jun 12, 2010 at 9:29 PM, David Glick davidgl...@groundwire.org wrote:
Has the process of reviewing RestrictedPython against a new Python
release been documented anywhere?
Not that I know of. Stephan Richter and Sidnei da Silva were the last
to do these reviews, maybe they know.
Hanno
On Sun, Jun 13, 2010 at 2:50 PM, Tres Seaver tsea...@palladion.com wrote:
On the whole, I would actually favor getting a 2.13.0 out even sooner
than Hanno suggests, to get it used (and therefore more polished)
sooner. With the post-eggification reduction in Zope2's scope, I think
a six month
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jonas Meurer wrote:
thus i suggest to either provide monolithic tarballs which do contain
the debendencies, or change release policy for the dependencies to not
break backwards compability with every minor release.
I think this discussion
On 2010-06-13, at 1348, Hanno Schlichting wrote:
On Sat, Jun 12, 2010 at 9:29 PM, David Glick davidgl...@groundwire.org
wrote:
Has the process of reviewing RestrictedPython against a new Python
release been documented anywhere?
Not that I know of. Stephan Richter and Sidnei da Silva were
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jonas Meurer wrote:
hey,
On 12/06/2010 Hanno Schlichting wrote:
What do we have in Zope 2.13:
[...]
Comments, suggestions, more work you'd like to get into 2.13?
another build system would be magnificent :-)
the new build system in
On Sunday, June 13, 2010, Hanno Schlichting wrote:
On Sat, Jun 12, 2010 at 9:29 PM, David Glick davidgl...@groundwire.org
wrote:
Has the process of reviewing RestrictedPython against a new Python
release been documented anywhere?
Not that I know of. Stephan Richter and Sidnei da Silva
hey,
On 12/06/2010 Hanno Schlichting wrote:
What do we have in Zope 2.13:
[...]
Comments, suggestions, more work you'd like to get into 2.13?
another build system would be magnificent :-)
the new build system in zope2.12 makes it hard/impossible to distribute
zope2 binaries within
13 matches
Mail list logo
