Hanno Schlichting wrote:
Hanno Schlichting wrote:
I'd like to propose to merge the philikon-aq branch into Zope trunk
aka Zope 2.12.
[...]
Timeline:
I would like to do the merge as soon as possible, so people can easily
test it against all their applications and report back problems.
Hi.
Hanno Schlichting wrote:
I'd like to propose to merge the philikon-aq branch into Zope trunk aka
Zope 2.12.
[...]
Timeline:
I would like to do the merge as soon as possible, so people can easily
test it against all their applications and report back problems.
Just as a note for
Martijn Faassen wrote:
Tres Seaver wrote:
[snip]
The second problem that might arise, is that the implicit assumption
that every object inside Zope 2 inherits from Acquisition base
classes no longer holds. Code that relies on the various aq_*
attributes to be there need to be adjusted to use
Tres Seaver wrote:
The second problem that might arise, is that the implicit assumption
that every object inside Zope 2 inherits from Acquisition base classes
no longer holds. Code that relies on the various aq_* attributes to be
there need to be adjusted to use the Acquisition methods
Tres Seaver wrote:
[snip]
The second problem that might arise, is that the implicit assumption
that every object inside Zope 2 inherits from Acquisition base classes
no longer holds. Code that relies on the various aq_* attributes to be
there need to be adjusted to use the Acquisition methods
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philipp von Weitershausen wrote:
Tres Seaver wrote:
The second problem that might arise, is that the implicit assumption
that every object inside Zope 2 inherits from Acquisition base classes
no longer holds. Code that relies on the various aq_*
Martin Aspeli wrote:
Hanno Schlichting wrote:
Philipp von Weitershausen wrote:
Hanno Schlichting wrote:
Merging it into Zope trunk will get it into the Zope 2.12 release
which is at this point not scheduled yet, but is unlikely to get a
release before early 2009. This should give us plenty
Christian Theune wrote:
On Thu, Apr 17, 2008 at 12:43:25PM +0200, Martijn Pieters wrote:
On Thu, Apr 17, 2008 at 12:27 PM, Hanno Schlichting [EMAIL PROTECTED] wrote:
I would like to do the merge as soon as possible, so people can easily test
it against all their applications and report back
Hanno Schlichting wrote:
Timeline:
I would like to do the merge as soon as possible, so people can easily
test it against all their applications and report back problems.
Merging it into Zope trunk will get it into the Zope 2.12 release which
is at this point not scheduled yet, but is
Hey,
Hanno, this is a major step forward! +1 from me as well.
Regards,
Martijn
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
Previously Philipp von Weitershausen wrote:
This sounds good. Here's another idea, though: In accordance with
release early and often, how about scheduling the 2.12 release shortly
after the 2.11 one? So the only new thing in 2.12 would be the
philikon-aq branch (it would still ship with
Philipp von Weitershausen wrote:
Hanno Schlichting wrote:
Merging it into Zope trunk will get it into the Zope 2.12 release
which is at this point not scheduled yet, but is unlikely to get a
release before early 2009. This should give us plenty of time to test.
This sounds good. Here's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hanno Schlichting wrote:
Hi.
I'd like to propose to merge the philikon-aq branch into Zope trunk aka
Zope 2.12.
Scope:
For those unfamiliar with the branch, it makes Acquisition aware of
__parent__ pointers. This makes it unnecessary to
Hanno Schlichting wrote:
Philipp von Weitershausen wrote:
Hanno Schlichting wrote:
Merging it into Zope trunk will get it into the Zope 2.12 release
which is at this point not scheduled yet, but is unlikely to get a
release before early 2009. This should give us plenty of time to test.
This
14 matches
Mail list logo
