-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Jung wrote:
--On 9. Mai 2006 17:32:06 -0700 Alec Mitchell [EMAIL PROTECTED] wrote:
On 5/9/06, Andreas Jung [EMAIL PROTECTED] wrote:
Hi,
I plan to release Zope 2.9.3 by this weekend. The release contains
some important fixes and a
On 4/20/06, Dieter Maurer [EMAIL PROTECTED] wrote:
Tres Seaver wrote at 2006-4-19 15:30 -0400:
...
Is Alec's traversal patch or Dieter's alternative being considered?
I'll note that I have a client who can't move forward from 2.9.1 to
2.9.3 because the changes to traversal semantics in
Tres Seaver wrote at 2006-4-19 15:30 -0400:
...
Is Alec's traversal patch or Dieter's alternative being considered?
I'll note that I have a client who can't move forward from 2.9.1 to
2.9.3 because the changes to traversal semantics in that release break
every view lookup in the application
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dieter Maurer wrote:
Tres Seaver wrote at 2006-4-19 15:30 -0400:
...
Is Alec's traversal patch or Dieter's alternative being considered?
I'll note that I have a client who can't move forward from 2.9.1 to
2.9.3 because the changes to traversal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
Previously Philipp von Weitershausen wrote:
After consulting with Andreas, there will be a Zope 2.9.3 bugfix release
next Monday. It will contain some more Zope 3 packages that were
forgotten in the initial Zope 2.9 release
--On 19. April 2006 15:30:44 -0400 Tres Seaver [EMAIL PROTECTED]
wrote:
I'll note that I have a client who can't move forward from 2.9.1 to
2.9.3 because the changes to traversal semantics in that release break
every view lookup in the application (which was originally built on
2.8.x, and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Jung wrote:
--On 19. April 2006 15:30:44 -0400 Tres Seaver [EMAIL PROTECTED]
wrote:
I'll note that I have a client who can't move forward from 2.9.1 to
2.9.3 because the changes to traversal semantics in that release break
every
--On 19. April 2006 15:55:44 -0400 Tres Seaver [EMAIL PROTECTED]
wrote:
The discussion on the list of the fix didn't take into account all the
usage patterns.
I would vote to delay a release until we find a way to restore the
broken functionality. Could we perhaps provide an alternate
