[z3-five] Goals for Five 1.1

[Philipp von Weitershausen]

Hello all,

now that Five 1.0.1 is out and that nasty unicode problem is finally 
taken care of, I would like to collect a list of goals for the upcoming 
release, Five 1.1.

Here's what I have so far:

* i18n support. This is coming from Lennart and me. A 1.0 branch-based 
implementation is sitting in the philikon-i18n branch. It needs to be 
reviewed, discusses, tested (esp. unit tests) and merged.

* atomic testing framework. Five 1.0.x simply loads up the FiveTest 
product, nearly all tests make assertions against what is implemented 
and registered in that product. FiveTest was broken down into smaller 
pieces during the reorganization to make tests more atomic from an 
organizational point of view. From a registration point of view, 
however, they're still not atomic because tests don't clean up after 
themselves. The goal here is to make the test suites clean up after 
having run their tests (cleaning up after every test would be way too 
expensive and probably unnecessary). I already have code for this in my 
sandbox.


Please add your goals for Five 1.1 to this list. In any case, though, I 
would suggest we keep this release small. Release early and often has 
always been a good choice in my opinion. Not that I don't want to see 
more features in Five, I just think it's a good idea to spread the work 
over several releases.

Having said that, I can imagine Five 1.1 being the last released based 
on Zope X3.0, though. Stephan Richter tells me Zope 3.1 will beta next 
week, and 3.1 contains *a lot* of improvements, little and big. 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.

Thoughts?

Philipp