[Zope-dev] Re: Zope 2.9.3 release

2006-05-10 Thread Tres Seaver
-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

Re: [Zope-dev] Re: Zope 2.9.3 release

2006-04-20 Thread Alec Mitchell
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 se

Re: [Zope-dev] Re: Zope 2.9.3 release

2006-04-20 Thread Tres Seaver
-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 t

Re: [Zope-dev] Re: Zope 2.9.3 release

2006-04-20 Thread Dieter Maurer
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 applicati

Re: [Zope-dev] Re: Zope 2.9.3 release

2006-04-19 Thread Philipp von Weitershausen
Andreas Jung 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 >> implementation with the original lookup orde

Re: [Zope-dev] Re: Zope 2.9.3 release

2006-04-19 Thread Andreas Jung
--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

Re: [Zope-dev] Re: Zope 2.9.3 release

2006-04-19 Thread Philipp von Weitershausen
Tres Seaver wrote: > 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 view loo

Re: [Zope-dev] Re: Zope 2.9.3 release

2006-04-19 Thread Lennart Regebro
On 4/19/06, Tres Seaver <[EMAIL PROTECTED]> wrote: > I would vote to delay a release until we find a way to restore the > broken functionality. Could we perhaps provide an alternate > implementation with the original lookup order, and make it pluggable? Possibly. But more interestingly, can you p

Re: [Zope-dev] Re: Zope 2.9.3 release

2006-04-19 Thread Tres Seaver
-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 bre

Re: [Zope-dev] Re: Zope 2.9.3 release

2006-04-19 Thread Andreas Jung
--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 w

[Zope-dev] Re: Zope 2.9.3 release

2006-04-19 Thread Tres Seaver
-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 r