[z3-five] Goals for Five 1.1

[Philipp von Weitershausen]

Martijn Faassen wrote:
>> Of course, all that largely depends on for how long the projects
>> with commercial interest (Silva, CPS, etc.) want to be based on X3.0
>> rather than 3.1. Of course, we also have an obligation towards X3.0
>> because of Zope 2.8, and the question is whether it's good to limit
>> Zope 2.8 to the Five 1.1.x branch.
> 
> Since Five exposes a fairly well controlled subset of Zope X3.0 to Zope 
> 2, I expect porting code over to Zope 3.1 is fairly easy.

Well, Five also duplicates a lot of code, often for trivial 
compatability reasons (because you can't mix new-style classes with 
extension classes, for example). We basically would have to review every 
piece of functionality and compare it with the changes it has undergone 
from Zope X3.0 to 3.1.

> I'd expect though that except if you're really bleeding edge, we target 
> Zope X3.0 for any Five releases for Zope 2.8.

Yeah, it wouldn't make much sense changing Zope 3 releases in the Zope 
2.8 bundle somewhere in between.

Concerning Five, I wonder how long we shall support 2.7 as a platform, 
given the problems with extension classes...

> I am hoping to get Zope 3.1 included in Zope 2.9. Gah, these version 
> numbers make me dizzy. :)

Heh :). But I agree with you.

Btw, one thing I would like to see resolved for Five 1.1 are the 
outstanding unit tests. When I fixed the whole unicode problem for 
forms, I ended up writing a couple of tests for other components I had 
to fix along the way (most prominently browser.adding); some of these 
components couldn't have been tested even manually because they were 
severely broken.
So, we are still lacking some tests (see TODO.txt) and svn blames most 
of the code on you, Martijn. :)

Philipp