Re: Zope3 name

I don't want to spend too much time on this naming issue. Introducing
new names will definitely not make things clearer.

The facts are that


a) "Zope 3" is already known under that name and Jim has made clear that
he won't change THAT name. So it might be a problem that the difference
between 2.7 and 3.0 is just 0.3, but we can't change that. And there are
a lot of examples in the OS community that suggest that people are well
aware of major incompatibilities (or changes at least):

KDE 1 => 2 => 3 (not binary compatible, 1 and 2 are REALLY different
even on part of the API)

Apache 1 => 2 ( Apache 1 modules will not work with Apache 2)

Linux 1.x => 2.x (not binary compatible; all code had to be recompiled)


b) It is important to make sure that "Zope 3X" (old name) is not Zope
3.x, so people don't expect it to be ready for production and to contain
the tools for Zope 2 compatibility ...


So let's focus on a distinctive mark for the experimental release. If
Zope X3 is not enoguh, let's say Zope EXPERIMENTAL 3 or something like that.

I strongly oppose Zope Component Server. As I've explained before, this
will ADD to the confusion because people will actually confuse it with
Zope in general, not only with Zope 3 ...

Joachim



-- 

iuveno AG

Joachim Werner

_________________

Wittelsbacherstr. 23b
90475 Nürnberg

[email protected]
www.iuveno.de

Tel.: +49 (0) 911/ 9 88 39 84