Hi everyone, It is finally here! Thanks goes to everyone who involved! January 29, 2009 - The Zope 3 development team announces the Zope 3.4.0 release. After 2 years of development, the Zope Foundation and the larger Zope community is proud to announce the release of Zope 3.4.0. The focus of the Zope 3.4 development effort has been the conversion from a monolithic source tree, to a set of many small packages (eggs), that can be used independently of each other. The core has been further stabilized through numerous bug fixes, and many new add-on packages have been developed to provide a richer development experience. With this release also comes a renewed commitment to a short and reliable release cycle of 6 months. Packages and Eggs ----------------- Zope 3 is now fully converted to an egg-based system. While some work still remains, it integrates very well with the rest of the Python community. The conversion to egg-based packaging also enables other Python developers to only have to use small bits and pieces of the complete Zope software system. The conversion means that Zope 3 developers do not use the classic Zope 3 tar-ball release anymore. However, for your convenience, Zope 3 developers will provide the classic Zope 3 tar ball releases for at least the 3.4 series and probably for 3.5 as well. So how are Zope 3 applications built using only eggs? The Known Good Set (KGS) ~~~~~~~~~~~~~~~~~~~~~~~~ The known good set -- or in short KGS -- is a configuration of packages and their versions that are known to work well together. The compatibility is frequently verified by running over twelve thousand tests on a daily basis [1]_. The KGS is tested against Python 2.4 and 2.5 on the 32- and 64-bit platforms. The list of controlled packages and their versions for Zope 3.4 can be found at the Zope 3 KGS site [2]_. The KGS can be used in several ways [3]_. The most common way is to "nail" the versions by downloading the version configuration file [4]_ and insert them as follows in your buildout configuration:: [buildout] versions = versions ... [versions] zope.interface = 3.4.0 ... ``zopeproject`` Project Builder ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To start building a project using a common setup, a package called `zopeproject` can be used to quickly setup the boilerplate for the project. Ample documentation is provided at the `zopeproject` home page [5]_. `zopeproject` uses Paste or ZDaemon to create a working server. The following commands get you started:: $ easy_install zopeproject $ zopeproject HelloWorld $ cd HelloWorld $ bin/helloworld-ctl foreground Demo Packages ~~~~~~~~~~~~~ At this point, there is no demo package demonstrating a simple Zope 3 application setup. However, the ``z3c.formdemo`` package can be used as a fairly minimal setup. To get started with it, enter the following:: $ svn co svn://svn.zope.org/repos/main/z3c.formdemo/tags/1.5.3 formdemo $ cd formdemo $ python bootstrap.py $ ./bin/buildout -v $ ./bin/demo fg .. [1] http://zope3.pov.lt/buildbot .. [2] http://download.zope.org/zope3.4/3.4.0/controlled-packages.cfg .. [3] http://download.zope.org/zope3.4/intro.html .. [4] http://download.zope.org/zope3.4/3.4.0/versions.cfg .. [5] http://pypi.python.org/pypi/zopeproject Downloads --------- - Zope 3.4 KGS: http://download.zope.org/zope3.4 - Zope 3.4 Controlled Packages: http://download.zope.org/zope3.4/3.4.0/controlled-packages.cfg - Zope 3.4 Versions: http://download.zope.org/zope3.4/3.4.0/versions.cfg - The classic Zope 3 source release can be downloaded from: http://download.zope.org/zope3.4/3.4.0/Zope-3.4.0.tgz Installation instructions for both Windows and Un*x/Linux are now available in the top level `README.txt` file of the distribution. The binary installer is recommended for Windows. Zope 3.4 requires Python 2.4 or 3.5 to run. You must also have zlib installed on your system. Resources --------- - Zope 3 Development Web Site: http://wiki.zope.org/zope3 - Zope 3 Developers Mailing List: http://mail.zope.org/mailman/listinfo/zope-dev Retired: http://mail.zope.org/mailman/listinfo/zope3-dev - Zope 3 Users Mailing List: http://mail.zope.org/mailman/listinfo/zope-users - Bug tracker at launchpad: https://launchpad.net/zope3 - IRC Channel: #zope3-dev at irc.freenode.net About Zope 3 ------------ Zope 3 is a web application server that continues to build on the heritage of Zope. It was rewritten from scratch based on the latest software design patterns and the experiences of Zope 2. The component architecture is the very core of Zope 3 that allows developers to create flexible and powerful web applications. Compatibility with Zope 2 ~~~~~~~~~~~~~~~~~~~~~~~~~ Zope 3 is not upwards compatible with Zope 2. This means you cannot run Zope 2 applications in Zope 3. We continue to work on the transition from Zope 2 to Zope 3 by making Zope 2 use more and more of the Zope 3 infrastructure. This means that new code written in Zope 2 can benefit from Zope 3 technology. Also, with care, code can be written that works in both Zope 3 and Zope 2. This allows a Zope 2 application to slowly evolve towards Zope 3. Unchanged Zope 2 applications are never expected to work in Zope 3, however. About the Zope Foundation ------------------------- The Zope Foundation, based in Fredricksburg, Virginia, is a not-for-profit organisation that provides support for the Zope community and the Zope platform and its associated software. Its community includes the open source community of contributers as well as the community of businesses and organizations that use Zope.
YES! Thank you! On Sat, Jan 31, 2009 at 08:33, Stephan Richter <srichter@cosmos.phy.tufts.edu> wrote:
Hi everyone,
It is finally here! Thanks goes to everyone who involved!
January 29, 2009 - The Zope 3 development team announces the Zope 3.4.0 release.
After 2 years of development, the Zope Foundation and the larger Zope community is proud to announce the release of Zope 3.4.0.
The focus of the Zope 3.4 development effort has been the conversion from a monolithic source tree, to a set of many small packages (eggs), that can be used independently of each other. The core has been further stabilized through numerous bug fixes, and many new add-on packages have been developed to provide a richer development experience.
With this release also comes a renewed commitment to a short and reliable release cycle of 6 months.
Packages and Eggs -----------------
Zope 3 is now fully converted to an egg-based system. While some work still remains, it integrates very well with the rest of the Python community. The conversion to egg-based packaging also enables other Python developers to only have to use small bits and pieces of the complete Zope software system. The conversion means that Zope 3 developers do not use the classic Zope 3 tar-ball release anymore. However, for your convenience, Zope 3 developers will provide the classic Zope 3 tar ball releases for at least the 3.4 series and probably for 3.5 as well.
So how are Zope 3 applications built using only eggs?
The Known Good Set (KGS) ~~~~~~~~~~~~~~~~~~~~~~~~
The known good set -- or in short KGS -- is a configuration of packages and their versions that are known to work well together. The compatibility is frequently verified by running over twelve thousand tests on a daily basis [1]_. The KGS is tested against Python 2.4 and 2.5 on the 32- and 64-bit platforms. The list of controlled packages and their versions for Zope 3.4 can be found at the Zope 3 KGS site [2]_.
The KGS can be used in several ways [3]_. The most common way is to "nail" the versions by downloading the version configuration file [4]_ and insert them as follows in your buildout configuration::
[buildout] versions = versions ...
[versions] zope.interface = 3.4.0 ...
``zopeproject`` Project Builder ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To start building a project using a common setup, a package called `zopeproject` can be used to quickly setup the boilerplate for the project. Ample documentation is provided at the `zopeproject` home page [5]_. `zopeproject` uses Paste or ZDaemon to create a working server. The following commands get you started::
$ easy_install zopeproject $ zopeproject HelloWorld $ cd HelloWorld $ bin/helloworld-ctl foreground
Demo Packages ~~~~~~~~~~~~~
At this point, there is no demo package demonstrating a simple Zope 3 application setup. However, the ``z3c.formdemo`` package can be used as a fairly minimal setup. To get started with it, enter the following::
$ svn co svn://svn.zope.org/repos/main/z3c.formdemo/tags/1.5.3 formdemo $ cd formdemo $ python bootstrap.py $ ./bin/buildout -v $ ./bin/demo fg
.. [1] http://zope3.pov.lt/buildbot
.. [2] http://download.zope.org/zope3.4/3.4.0/controlled-packages.cfg
.. [3] http://download.zope.org/zope3.4/intro.html
.. [4] http://download.zope.org/zope3.4/3.4.0/versions.cfg
.. [5] http://pypi.python.org/pypi/zopeproject
Downloads ---------
- Zope 3.4 KGS: http://download.zope.org/zope3.4
- Zope 3.4 Controlled Packages: http://download.zope.org/zope3.4/3.4.0/controlled-packages.cfg
- Zope 3.4 Versions: http://download.zope.org/zope3.4/3.4.0/versions.cfg
- The classic Zope 3 source release can be downloaded from: http://download.zope.org/zope3.4/3.4.0/Zope-3.4.0.tgz
Installation instructions for both Windows and Un*x/Linux are now available in the top level `README.txt` file of the distribution. The binary installer is recommended for Windows.
Zope 3.4 requires Python 2.4 or 3.5 to run. You must also have zlib installed on your system.
Resources ---------
- Zope 3 Development Web Site: http://wiki.zope.org/zope3
- Zope 3 Developers Mailing List: http://mail.zope.org/mailman/listinfo/zope-dev
Retired: http://mail.zope.org/mailman/listinfo/zope3-dev
- Zope 3 Users Mailing List: http://mail.zope.org/mailman/listinfo/zope-users
- Bug tracker at launchpad: https://launchpad.net/zope3
- IRC Channel: #zope3-dev at irc.freenode.net
About Zope 3 ------------
Zope 3 is a web application server that continues to build on the heritage of Zope. It was rewritten from scratch based on the latest software design patterns and the experiences of Zope 2.
The component architecture is the very core of Zope 3 that allows developers to create flexible and powerful web applications.
Compatibility with Zope 2 ~~~~~~~~~~~~~~~~~~~~~~~~~
Zope 3 is not upwards compatible with Zope 2. This means you cannot run Zope 2 applications in Zope 3.
We continue to work on the transition from Zope 2 to Zope 3 by making Zope 2 use more and more of the Zope 3 infrastructure. This means that new code written in Zope 2 can benefit from Zope 3 technology. Also, with care, code can be written that works in both Zope 3 and Zope 2. This allows a Zope 2 application to slowly evolve towards Zope 3. Unchanged Zope 2 applications are never expected to work in Zope 3, however.
About the Zope Foundation -------------------------
The Zope Foundation, based in Fredricksburg, Virginia, is a not-for-profit organisation that provides support for the Zope community and the Zope platform and its associated software. Its community includes the open source community of contributers as well as the community of businesses and organizations that use Zope. _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
-- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64
2009/1/31 Stephan Richter <srichter@cosmos.phy.tufts.edu>:
Hi everyone,
It is finally here! Thanks goes to everyone who involved!
Thank you! BTW, there's some problems with python version requirement in the "tarball" release. It does not accept python 2.5 while it should as stated in the announcement. -- WBR, Dan Korostelev
On Saturday 31 January 2009, Dan Korostelev wrote:
BTW, there's some problems with python version requirement in the "tarball" release. It does not accept python 2.5 while it should as stated in the announcement.
Sigh, I only tested by specifying the Python version directly. I am too lazy to fix it now. :-) If someone fixes the configure file and sends me a new TGZ, I'll upload it. On the other hand, I am glad to see that people are testing out the TGZ release and give it a spin. I guess we will have a 3.4.1 release soonish. BTW, would someone like to help out with releases? Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter"
Yay! Thanks for all that work, Stephan! Regards, Martijn
Stephan Richter wrote:
It is finally here! Thanks goes to everyone who involved!
January 29, 2009 - The Zope 3 development team announces the Zope 3.4.0 release.
Excellent! I have to say, though, that the download process is quite confusing. Let's say I'm a Pythonista who wants to try out Zope 3. Google sends me here: http://download.zope.org/zope3.4/ After the release overview, the document tells me Zope is now distributed as eggs. I'm familiar with eggs and I like them. Then it talks about the KGS and my buildout. It tells me how to modify my buildout configuration. Wait, what's a buildout and how do I configure it? Hmm, none of the links about the KGS tell me much about this buildout thing. I can already tell it's gonna be hard to learn about Zope... Well, I'll skip over the KGS stuff and see what I can figure out anyway. Ok, I can follow the easy_install directions. I'm really savvy and I'll even use virtualenv to do it, even though the document doesn't mention that. I already have the habit of using virtualenv whenever I use easy_install. So, following the directions, I create a project called HelloWorld. I try to fire it up. Uh-oh... zope.configuration.config.ConfigurationExecutionError: <class 'zope.configuration.exceptions.ConfigurationError'>: Help Topic definition [...]/transaction-1.0a1-py2.5.egg/transaction/README.txt does not exist So it breaks before even starting the server. This is really trying my patience, but I study a lot of web pages and discuss the problem with other developers over a few days. Following a friend's recommendation, I add the following two lines to the [buildout] section of buildout.cfg generated by zopeproject: extends = http://download.zope.org/zope3.4/3.4.0/versions.cfg versions = versions After running bin/buildout again, the server finally starts! Of course, what I see when the server starts is opaque and uninviting, but I'll leave that for another discussion. :-) So, my question is: what should the download page *really* say? Consider that existing developers of Zope 3 don't actually need this page at all since they already use zc.buildout. This page's audience, then, is people who know little about zc.buildout, let alone the KGS. Newbies need straightforward directions to follow. Shane
On Saturday 31 January 2009, Shane Hathaway wrote:
So, my question is: what should the download page *really* say? Consider that existing developers of Zope 3 don't actually need this page at all since they already use zc.buildout. This page's audience, then, is people who know little about zc.buildout, let alone the KGS. Newbies need straightforward directions to follow.
I have purposely skipped a good "Getting Started" story for the Zope 3.4 release, because of time constraints. It is also one reason, why I am still so committed to the TGZ release. I really, really want to change that for Zoep 3.5, but I'll need help. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter"
On Sat, Jan 31, 2009 at 2:33 AM, Stephan Richter <srichter@cosmos.phy.tufts.edu> wrote:
- Zope 3.4 Versions: http://download.zope.org/zope3.4/3.4.0/versions.cfg
I had been using http://download.zope.org/zope3.4/versions.cfg, but that has gone away. Was I using the wrong thing? Was the removal of the old file intentional? -- Benji York Senior Software Engineer Zope Corporation
On Mon, Feb 2, 2009 at 15:04, Benji York <benji@zope.com> wrote:
<srichter@cosmos.phy.tufts.edu> wrote:
- Zope 3.4 Versions: http://download.zope.org/zope3.4/3.4.0/versions.cfg
I had been using http://download.zope.org/zope3.4/versions.cfg, but that has gone away. Was I using the wrong thing? Was the removal of the old file intentional?
http://download.zope.org/zope3.4/3.4.0/versions.cfg KGS 1.x uses new anatomy (major/minor/): http://download.zope.org/zope3.4/intro.html Cheers -- Sebastien Douche <sdouche@gmail.com>
On Feb 2, 2009, at 9:28 AM, Sebastien Douche wrote:
KGS 1.x uses new anatomy (major/minor/): http://download.zope.org/zope3.4/intro.html
Am I the only one who finds those pale green links on a white background quite unreadable? The code examples with that same color on dark grey are OK, but such a pale color on white just doesn't work. At least for me. Regards, Zvezdan
On Monday 02 February 2009, Zvezdan Petkovic wrote:
On Feb 2, 2009, at 9:28 AM, Sebastien Douche wrote:
KGS 1.x uses new anatomy (major/minor/): http://download.zope.org/zope3.4/intro.html
Am I the only one who finds those pale green links on a white background quite unreadable?
The code examples with that same color on dark grey are OK, but such a pale color on white just doesn't work.
At least for me.
It's an Open Source project. :-) Go into zope.release/src/zope/release/templates and fix the layout at your hearts content. Send us a before and after screenshot so that we all agree it is an improvement. Updating the site is a matter of calling a script. BTW, as I see from your E-mail address you are working for Zope Corp. and you should be well indoctrinated in Open Source. :-) Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter"
On Mon, Feb 2, 2009 at 16:28, Sebastien Douche <sdouche@gmail.com> wrote:
On Mon, Feb 2, 2009 at 15:04, Benji York <benji@zope.com> wrote:
<srichter@cosmos.phy.tufts.edu> wrote:
- Zope 3.4 Versions: http://download.zope.org/zope3.4/3.4.0/versions.cfg
I had been using http://download.zope.org/zope3.4/versions.cfg, but that has gone away. Was I using the wrong thing? Was the removal of the old file intentional?
http://download.zope.org/zope3.4/3.4.0/versions.cfg
KGS 1.x uses new anatomy (major/minor/): http://download.zope.org/zope3.4/intro.html
Cheers
Yes, and still it broke all of my branches as now I will have to update a whole lot of checkouts to get them working again. So while I am all for the new system, maybe we can keep the old url for backwards compatibility, please? Ignas
On Monday 02 February 2009, Ignas Mikalajunas wrote:
Yes, and still it broke all of my branches as now I will have to update a whole lot of checkouts to get them working again. So while I am all for the new system, maybe we can keep the old url for backwards compatibility, please?
So you are in a lot of pain, huh? I guess I could add a couple lines to the generate-site script to make this happen. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter"
On Mon, Feb 2, 2009 at 17:12, Stephan Richter <srichter@cosmos.phy.tufts.edu> wrote:
On Monday 02 February 2009, Ignas Mikalajunas wrote:
Yes, and still it broke all of my branches as now I will have to update a whole lot of checkouts to get them working again. So while I am all for the new system, maybe we can keep the old url for backwards compatibility, please?
So you are in a lot of pain, huh? I guess I could add a couple lines to the generate-site script to make this happen.
Thank you, I really appreciate it. I will need at least a couple of days to push the update to "everywhere". Distributed version control systems make this a bit more cumbersome, as there are tens of branches in the wild and merge from trunk is something that you don't do that often, especially when working on a feature. Ignas
On Monday 02 February 2009, Benji York wrote:
On Sat, Jan 31, 2009 at 2:33 AM, Stephan Richter
<srichter@cosmos.phy.tufts.edu> wrote:
- Zope 3.4 Versions: http://download.zope.org/zope3.4/3.4.0/versions.cfg
I had been using http://download.zope.org/zope3.4/versions.cfg, but that has gone away. Was I using the wrong thing? Was the removal of the old file intentional?
Yeah, the unversioned links are the only ones that I did not maintain. You now use a reference to the version directly. http://download.zope.org/zope3.4/3.4.0/versions.cfg How much pain is that for you? :-) Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter"
2009/2/2 Stephan Richter <srichter@cosmos.phy.tufts.edu>:
Yeah, the unversioned links are the only ones that I did not maintain. You now use a reference to the version directly.
BTW, why so? It's quite handy to be able to say - "just use the latest release from the 3.4 branch, whatever version number it has", because there are bug fixes and no backward-incompatibilites expected. -- WBR, Dan Korostelev
On Monday 02 February 2009, Dan Korostelev wrote:
2009/2/2 Stephan Richter <srichter@cosmos.phy.tufts.edu>:
Yeah, the unversioned links are the only ones that I did not maintain. You now use a reference to the version directly.
BTW, why so? It's quite handy to be able to say - "just use the latest release from the 3.4 branch, whatever version number it has", because there are bug fixes and no backward-incompatibilites expected.
Nobody reacted to my E-mail when I asked for feedback. It was extra work and I tried to limit the scope of coding as much as possible. You don't want to know how much time I put into this release as it is. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter"
2009/2/2 Stephan Richter <srichter@cosmos.phy.tufts.edu>:
On Monday 02 February 2009, Dan Korostelev wrote:
2009/2/2 Stephan Richter <srichter@cosmos.phy.tufts.edu>:
Yeah, the unversioned links are the only ones that I did not maintain. You now use a reference to the version directly.
BTW, why so? It's quite handy to be able to say - "just use the latest release from the 3.4 branch, whatever version number it has", because there are bug fixes and no backward-incompatibilites expected.
Nobody reacted to my E-mail when I asked for feedback. It was extra work and I tried to limit the scope of coding as much as possible. You don't want to know how much time I put into this release as it is.
Hey, no offence meant! The current state is great for me, personally, I just asked :) Sorry, I missed that email. But you guys did a great work preparing zope.release. -- WBR, Dan Korostelev
On Monday 02 February 2009, Dan Korostelev wrote:
Hey, no offence meant! The current state is great for me, personally, I just asked :)
I don't feel offended; I just try to explain why I did not do certain things. :-) Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter"
On Mon, Feb 02, 2009 at 07:20:10AM -0800, Stephan Richter wrote:
On Monday 02 February 2009, Dan Korostelev wrote:
2009/2/2 Stephan Richter <srichter@cosmos.phy.tufts.edu>:
Yeah, the unversioned links are the only ones that I did not maintain. You now use a reference to the version directly.
BTW, why so? It's quite handy to be able to say - "just use the latest release from the 3.4 branch, whatever version number it has", because there are bug fixes and no backward-incompatibilites expected.
Nobody reacted to my E-mail when I asked for feedback.
Does that surprise you? (BTW I reacted. I didn't say I was personally going to be in a lot of pain, but I suggested keeping old URLs working the cheapest way I could imagine -- via Apache rewrite rules.)
It was extra work and I tried to limit the scope of coding as much as possible. You don't want to know how much time I put into this release as it is.
And we're immensely grateful. Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development
On Mon, Feb 2, 2009 at 16:20, Stephan Richter <srichter@cosmos.phy.tufts.edu> wrote:
Nobody reacted to my E-mail when I asked for feedback. It was extra work and I tried to limit the scope of coding as much as possible. You don't want to know how much time I put into this release as it is.
I obviously didn't read it properly. :) It's no panic, but yeah, I think automatic upgrades like that would be a nice option. But it might be something that could be a part of the buildout recipe. But admittedly it's really mostly only useful for developers, wouldn't want production machines to upgrade without me being explicit about it. -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64
On Mon, Feb 2, 2009 at 10:10 AM, Stephan Richter <srichter@cosmos.phy.tufts.edu> wrote:
On Monday 02 February 2009, Benji York wrote:
On Sat, Jan 31, 2009 at 2:33 AM, Stephan Richter
<srichter@cosmos.phy.tufts.edu> wrote:
- Zope 3.4 Versions: http://download.zope.org/zope3.4/3.4.0/versions.cfg
I had been using http://download.zope.org/zope3.4/versions.cfg, but that has gone away. Was I using the wrong thing? Was the removal of the old file intentional?
Yeah, the unversioned links are the only ones that I did not maintain. You now use a reference to the version directly.
http://download.zope.org/zope3.4/3.4.0/versions.cfg
How much pain is that for you? :-)
It's not that much pain. It's also not a good way to encourage people to like and use the KGS. -- Benji York Senior Software Engineer Zope Corporation
participants (10)
-
Benji York -
Dan Korostelev -
Ignas Mikalajunas -
Lennart Regebro -
Marius Gedminas -
Martijn Faassen -
Sebastien Douche -
Shane Hathaway -
Stephan Richter -
Zvezdan Petkovic