Few days back Stephan Richter released Zope 3.4 second beta release.
The Zope 3.4 release may be the last release of Zope 3 release
as a single package. There is still a minor chance for a 3.5 release.
Anyway, Zope 3 as a single package is coming to an end. I won't be
surprised if the term "Zope 3" itself vanish in the future.
This is a good thing for the future of Zope project & community. As I
implied in one of my last post, Zope is becoming more "Pythonic".
Well, I am not going to describe "What is Pythonic" :) . You know,
Zope is even dropping the server business ! (Zope 3 used Twisted web
server as the default server for a long time). We also retired
zope3-dev list last month .
For those who using Zope 3.3 or earlier versions, Zope 3.4 is a chance
(may be last) for migrating to egg and buildout based system for
development and deployment.
Now you might wonder, "Where is Zope going ?" . This is a very
difficult question for me to answer, so, I refrain from trying it :)
Here I am just giving two pointers: Grok, Repoze.
However, I believe Zope 3 will live for a long time through the
numerous packages derived from it.
Update:I forgot another pointer: zopeproject
The Zope 3.4 release may be the last release of Zope 3 release
as a single package. There is still a minor chance for a 3.5 release.
Anyway, Zope 3 as a single package is coming to an end. I won't be
surprised if the term "Zope 3" itself vanish in the future.
This is a good thing for the future of Zope project & community. As I
implied in one of my last post, Zope is becoming more "Pythonic".
Well, I am not going to describe "What is Pythonic" :) . You know,
Zope is even dropping the server business ! (Zope 3 used Twisted web
server as the default server for a long time). We also retired
zope3-dev list last month .
For those who using Zope 3.3 or earlier versions, Zope 3.4 is a chance
(may be last) for migrating to egg and buildout based system for
development and deployment.
Now you might wonder, "Where is Zope going ?" . This is a very
difficult question for me to answer, so, I refrain from trying it :)
Here I am just giving two pointers: Grok, Repoze.
However, I believe Zope 3 will live for a long time through the
numerous packages derived from it.
Update:I forgot another pointer: zopeproject

Comments
I use plone this day, in the past I tried to understand
zope but after a while I gave up.
Python is excellent and very well documented.
For zope I downloaded the last documentation pdf
which is for zope 2.6 or I looked at to http://www.plope.com/Books/2_7Edition
which is the "actual" zope book.
Or I looked in the (z)wiki's not knowing if the stuff is actual or outdated.
At least for me, actually it looks like zope is from zope developers for zope developers, or
people who have a lot of time to play adventure games ...
This is what reminds me The Da Vinci Code book ... always
running around and trying to understand the puzzle.
I headr about Grok and Repoze BUT..
there should be *one* main place (zope.org would be the one)
where you can go and where you get "the" information:
I need to have something I can call zope)
If zope is no more zope, ... then what is zope??
If zope is a bag of egg's, then is it still zope ?
John
I used Zope 3 a bit and it was pretty nice but then it happened... eggs, buildouts, changes, changes, changes. Is there any Z3 user (and not Z3 developer) who is able to stay up to date with that? Anyone knows how to use it? I don't have time for that so I'm Django guy now and I'm very happy with this.
Z3 developers - if you want to have some users give them some __good__ and __up to date__ documentation!
Look at worldcookery appetizers - much of them is outdated. Look at z3/z3c products - do I really have to browse through doctests and code to get to know what are they doing and how to use them? Now Z3 is a bunch of packages, or rather there is a bunch of packages that you can get and configure to have Z3. Where is list of the packages and their descriptions? Sample use cases?
Zope is great but using Zope is hard (if you're not a z3-developer :p).
On the other side Django has a documentation that is always up to date - it describes not only stable versions, it describes latest trunk too. This is great.
I agree with you, we need more up-to-date documentation.
It requires lots effort, in fact I started some efforts in Wiki,
unfortunately, it is again out of date: http://wiki.zope.org/zope3/ZopeGuid
Now I am working on documenting Zope Component Architecture:
http://www.muthukadan.net/docs/zca.h
http://www.muthukadan.net/docs/zca.pdf
If anyone want to join in this effort, you can join me here:
https://edge.launchpad.net/zcadoc
its great that you started a new documentation,
but as I stated in my first comment ..
wouldn't be zope3.org the better place (or
are you not allowed to do so).
I myself for example, do even not remember
when or how I discovered your blog.
So other people will probably not note that
you do such a great work ;-)
By the way: I also saw te Nuxeo switch to Java,
and this make me ask myself:
If zope is so great:
- why do they switch?
- and do the big transition work?
- I always thought that zope is scalable with zeo
(not really knowing how it works, I read only about it)
On the other side I noted:
- www.ubuntulinux.com did run plone in the first time
(or some part of their site)
Now they switched some big parts to MoinMoin wiki
- www.scipy.org did run plone in the first time,
now they use MoinMoin wiki for the whole site
Anton
http://wiki.zope.org/zope3/ComponentArc
(This page is the first link from Zope 3 wiki)
Also feel free to give a link to my book from any good place :)
I am sorry, I do not know much about Nuxeo or other things you mentioned.
I think better you can ask their team for the reason of the switch.
With thanks and regards,
Baiju M