Re: Message received :)

> Given the concerns raised, I'd like to encourage this group to
> continue helping with the communication about and planning of the
> transition.  Among other things, I'd like to get your input on:
>
> - The renaming of the thing currently known as Zope 3x, and


I'm glad this is under consideration. That 3x moniker isn't terribly 
obvious; it really is a "code name" but doesn't look like one. But I 
suppose this doesn't need to be a new "what-do-we-call-it" thread.

> - The release schedule for the thing currently known as Zope 3x.
>   My sense is that there is concern that we are making alpha
>   releases while the system is still in a state of flux.  While
>   this is consistent with my understanding of the meaning of "alpha"
>   releases, I understand why some folks feel this sends the wrong
>   message. I'm open to scaling these early releases back or calling
>   them something else. 

Releases are good. Some people just don't do CVS. Calling them "alphas" 
probably not so good: most folks (esp. those used to closed development) 
think that once an alpha shows up, the thing's pretty near done. I think 
the Mozilla terminology of Milestones would be appropriate here: it 
indicates that development is still ongoing and not yet near its 
destination, but that we're making releases to show progress and get 
feedback.

Milestones can have specific goals attached, but need not. (Although I 
think there's some great possiblities in tying them in with sprints.) 
They can simply be indicative of X level of progress.

Might even allow us to drop the whole codename thing and say "Zope 3 
won't have backwards compatibility built in until a later milestone."

Last release (only release, I suppose) was around the beginning of the 
year, right? Perhaps now would be a good time for Zope 3 M1 (or is it M2?)

          --jcc