-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
> Tres Seaver wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Jim Fulton wrote:
>>
>>> Martijn Faassen wrote:
>
> [snip]
>
Right, lib/python/zope is actually Zope X3.0.0, and we didn't expect
we'd
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
Martijn Faassen wrote:
[snip]
Right, lib/python/zope is actually Zope X3.0.0, and we didn't expect
we'd need to *update* Zope X3.0 in order for it to work with Zope 2.8.
The new ZODB version is having some repercussi
[Tres]
...
> I'll have to take your word for that; are you saying that
> 'svn:external' doesn't work by default in the windows SVN clients?
Crossed in the mail; no problem here.
...
> OK, that works for me. AFAIK, the branch should be ready to merge
> "whenever"; all the recent work on it ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Peters wrote:
> [Tres Seaver]
> ...
>
>>Most of that work has been done on the trunk. The 'five-integration'
>>branch changes consist largely of:
>>
>>- Setting up an 'svn:external' link to the Zope X3 3.0 repository
>> (which is on a branch, pr
...
[Tres]
>> - Setting up an 'svn:external' link to the Zope X3 3.0 repository
>> (which is on a branch, pruned to include only the packages which were
>> actually released with 3.0).
[Tim]
> Just noting that this may create new but short-lived problems for
> developers on Windows (can't te
[Tres Seaver]
...
> Most of that work has been done on the trunk. The 'five-integration'
> branch changes consist largely of:
>
> - Setting up an 'svn:external' link to the Zope X3 3.0 repository
> (which is on a branch, pruned to include only the packages which were
> actually released with 3
Chris McDonough <[EMAIL PROTECTED]> wrote:
> Brian Lloyd wrote:
> > A lot of time was spent talking about these (legitimate) concerns -
> > unfortunately it will probably take a little time to distill all
> > of that communication to the community. But let me take a shot ;)
> >
> > There are se
Chris McDonough wrote:
Yup, that makes sense. Are these assumed to also be the folks who will
try to make sure that new Z3 releases make it in to Z2 via Five? I
guess what I'm driving at is that I'd hate to eventually have a very old
version of Z3 sitting inside of Zope 2 due to insufficient band
Chris McDonough wrote:
[snip]
Please correct me if I'm wrong here but I get the sense that Five is
less of a "migration path" from Z2 to Z3 than a way to integrate Z3
technologies (like views and adapters) into Z2 right now. Obviously
allowing Z2 developers to use these things will give them a som
