I'm sorry, I don't really understand the current line of discussion yet.
I see a lot of discussion which part is going to be cut out and dropped,
or replaced. I haven't yet understood what's the end target for the
project.
So, are you guys expecting to get Zope into a shape where it will
attract
(Tue, Jun 28, 2011 at 12:57:02PM +0100) Laurence Rowe wrote/schrieb/egrapse:
> This is an update on today's security hotfix release.
Thank you for the update, most helpful!
> The fix will be released at 15:00 UTC today, Tuesday 28th June, 2011
> (11:00am US EDT.) Updated versions of Zope 2 contai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tres and all,
so it looks like I came over as a total jerk who rides a personal attack
on Hanno. That is of course not my intention, not at all. I am sorry for
that.
I am grateful for every improvement to the code and it looks like Hanno
did a great
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(Sun, Apr 17, 2011 at 02:58:12PM +0200) Charlie Clark wrote/schrieb/egrapse:
> As for an explanation of how to use events or simply getting a grasp of
> using the ZCA in Zope 2 I can highly recommend Philip von Weiterhausen's
> book on Zope 3. In m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(Sun, Apr 17, 2011 at 07:10:07AM -0400) Tres Seaver wrote/schrieb/egrapse:
> Moving a "big old application" across multiple major versions at onece
> of any platform is likely to be painful:
Tres,
I know how to move an app to newer zope versions. My
(Fri, Apr 15, 2011 at 02:39:26PM +0200) Hanno Schlichting wrote/schrieb/egrapse:
> > I assume this kind of thing has been discussed and the decision has been
> > taken on judging backwards compatibility vs. the benefits of doing this?
>
> The particular code was unused for several years,
Sigh. So
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Zope Developers,
I've asked about this on the zope@ list, without getting any replies.
Talking about it in #zope, I decided that maybe I will have to ask here
from another point of view.
As I was testing moving a big, old application to Zope 2
