[z3-five] Renamed the Zope package to Zope2 and including Zope 3 packages in Zope 2.8

[Martijn Faassen]

Jim Fulton wrote:
> Martijn Faassen wrote:
> 
>> Jim Fulton wrote:

>> Won't this delay Zope 2.8 even longer? Um, yeah, it will. :)
> 
[snip]
> No, it won't.  I'm happy to include some things that are
> already there, but I'm not going to spend any time on it
> beyond some svn cp commands.

Okay.. The issue still remains that having to juggle between different 
versions of packages will become a requirement for Five. It's unlikely 
you'll be able to include enough of Zope 3 to bootstrap Five completely, 
as it depends heavily on pieces of app, unless you just go and include 
almost all of Zope 3 in Zope 2.

This means that Five will have to worry about various versions of the 
Zope 3 modules that are around. The ones in the Zope 3 distribution that 
it requires, as well as the ones in Zope 2.8.

>>> I also want
>>> to use some of the Zope 3 persistent code support, which depends on
>>> zope.interface to help get ZClasses working again.
>>
>> I assume you need this for your own reasons, as I doubt many of us are 
>> depending on this or asking for it. I haven't touched ZClasses in 
>> about 4 or 5 years, myself, and I don't expect I will ever again...

> 
> I need this for backward compatibility. ZC doesn't use ZClasses.

They broke in Zope 2.8 and work in Zope 2.7? I haven't tracked ZClasses 
a lot, and figured they were broken longer.

>>> I haven't decided
>>> which parts of Zope 3 should be included in Zope 2.8 and would like to
>>> get input.  If you have suggestions on what to include or exclude,
>>> please respond here or on the zope-dev list, where I am also posting
>>> this message.
>>
>> My input would be not to do it and instead feature freeze Zope 2.8 so 
>> it can be finally released.
> 
> Well, I think we need at least zope.interface.

That one is stable enough not to cause too many version headaches, I hope...

>> I expect life for Five will only get harder once pieces of Zope 3 make 
>> it into Zope 2.8, as there will be two versions of Zope 3 code to deal 
>> with -- the stuff in Zope 3 proper and the version in Zope 2.8.
> 
> I'm happy to include very little, or a lot, as long as it doesn't
> affect the schedule.

I'd then suggest a minimum, as the more you include, the more chance 
exists of version skew between Zope 3 and Zope 2+3.

Regards,

Martijn