- Zope-Dev - Zope lists

Zope 3.3 common criteria derivative
by Christian Theune 07 Nov '07

07 Nov '07

Hi, the common criteria evaluation is using zc`s "Sharing" security policy. I need to specify a version number/name that describes the release to be evaluated. The most straight forward thing I can think of is to create a branch derived from the 3.3 release series that includes zc.sharing and is configured for using it in the common criteria evaluated way. A name proposal would be "Zope 3 Common Criteria Edition". The question would be whether to let it have it's own version number (1.0) or to start from the version number of Zope 3.3 that it was built on. Comments? Christian -- gocept gmbh & co. kg - forsterstrasse 29 - 06112 halle (saale) - germany www.gocept.com - ct(a)gocept.com - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development

3 4

Zope Tests: 5 OK
by Zope Tests Summarizer 07 Nov '07

07 Nov '07

Summary of messages to the zope-tests list. Period Tue Nov 6 13:00:00 2007 UTC to Wed Nov 7 13:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Tue Nov 6 20:53:19 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008606.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Tue Nov 6 20:54:49 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008607.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue Nov 6 20:56:20 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008608.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue Nov 6 20:57:50 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008609.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue Nov 6 20:59:20 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008610.html

1 0

Location of common criteria documentation
by Christian Theune 07 Nov '07

07 Nov '07

Hi, we're (still/again/...) working on the common criteria project. We're in a mode to try to finish it up and get done with. I feel that Zope3/trunk/doc/security is not the right location for those documents. I'd move them to a top level project in svn or something like Zope3/common-criteria/. Oppinions? Christian -- gocept gmbh & co. kg - forsterstrasse 29 - 06112 halle (saale) - germany www.gocept.com - ct(a)gocept.com - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development

2 1

Zope Tests: 5 OK
by Zope Tests Summarizer 06 Nov '07

06 Nov '07

Summary of messages to the zope-tests list. Period Mon Nov 5 13:00:00 2007 UTC to Tue Nov 6 13:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Mon Nov 5 20:53:55 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008601.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Mon Nov 5 20:55:26 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008602.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Mon Nov 5 20:56:56 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008603.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Mon Nov 5 20:58:26 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008604.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Mon Nov 5 20:59:56 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008605.html

1 0

SVN configuration guidelines
by Christian Theune 06 Nov '07

06 Nov '07

Hi, the most current version I found was this: http://www.zope.org/DevHome/Subversion/ZopeSVNFAQ Can we update the rules for setting the global ignores to include '.egg-info' directories? Christian -- gocept gmbh & co. kg - forsterstrasse 29 - 06112 halle (saale) - germany www.gocept.com - ct(a)gocept.com - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development

2 1

Current screenshots of Hivurt CMS
by Mikhail Kashkin 06 Nov '07

06 Nov '07

Hello! we are developing Zope3 based CMS called Hivurt. Some components already available on http://code.keysolutions.ru/svn/ (ZPL/GPL) we are heavily updating this repository this week, so If you like screenshots of new products then you are welcome http://www.flickr.com/photo_zoom.gne?id=1879568897&size=o Please, contact me personally if you have any questions or proposals. -- Mikhail Kashkin (http://keysolutions.ru/)

3 3

Zope 3.4.0 release and the KGS
by Stephan Richter 06 Nov '07

06 Nov '07

Hi everyone, as you saw, I released beta 2 of Zope 3.4.0 today after having completed the first KGS. I am pretty much ready for RC1, as soon as ZODB 3.8.0 final and zc.buildout 1.0.0 final have been released. From now on I am planning to move quickly and hope to get Zope 3.4.0 final out before Thanksgiving (Nov. 22). I would really like developers to test the KGS carefully, making sure that your applications will run with this combination of packages [1]_. Please make sure that no package's find-links points to http://download.zope.org/distribution anymore, since this directory contains package releases that mess with the KGS; in other words it has package versions greater than those in the KGS and will cause incorrect versions to be installed. .. [1] SchoolTool has already done so successfully. Thanks Ignas! Further, if you would like to see another package added to the KGS, let me know. Here is the workflow that I use to test new packages for the KGS: 1. Download and install the Zope 3.4 branch of the ``zope.release`` package:: # svn co svn://svn.zope.org/repos/main/zope.release/branches/3.4 \ zope.release-3.4 # cd zope.release-3.4 # python2.4 bootstrap.py # ./bin/buildout -N 2. Generate the KGS `buildout.cfg` file for testing:: # ./bin/generate-buildout 3. Build the KGS tests and run the tests:: # cd test # python2.4 ../bootstrap.py # ./bin/buildout -N # ./bin/test -vpc1 All tests should pass, but there is a lot of additional output. (It would be great, if people could help me reduce this noise.) 4. Add your package name and version to `controlled-packages.cfg` using this syntax:: [package-name] versions = 1.2.3 5. Regenerate the KGS `buildout.cfg`:: # ../bin/generate-buildout 6. Comment out the line starting with ``index = `` in the KGS `buildout.cfg` file, because your package and version combination might not be in the KGS yet. (I should probably not generate that line altogether.) 7. Build the KGS tests and run the tests again:: # ./bin/buildout -N # ./bin/test -vpc1 8. If all tests pass, you can check-in the new `controlled-packages.cfg` version and upload it to the KGS # cd .. # svn ci # ./bin/generate-versions # ./bin/generate-buildout # ./bin/upload Note: At this point, you might not be able to upload directly to http://download.zope.org/zope3.4, since the permissions might not be set up correctly. I will check with Jim about this. And that's it. I think the process is fairly simple once you get setup. BTW, you can think of the KGS as our new super-trunk. ;-) And finally, I have added two scripts (see `zope.pypisupport`) that allow us to manage the roles of users in PyPI packages via the command line. In particular, you can give a certain user the owner role for all packages for which you have owner/admin rights yourself. I have given the following people the owner role of all the packages that I am an owner of: J1m, fdrake, ctheune, philikon, baijum. This should avoid people-availability bottlenecks in the future. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training

1 0

Zope 3.4.0 beta 2 Released!
by Stephan Richter 06 Nov '07

06 Nov '07

November 5, 2007 - The Zope 3 development team announces the Zope 3.4.0b2 release. This release is the second beta release for Zope 3.4.0. It was preceded by an early beta 1 release back in July. Zope 3.4 introduces support for binary large objects in the ZODB, and provides a new postprocessing hook for publishing results. Many of the packages also provide small feature improvements that are too numerous to list at this point. Packages and Eggs ----------------- Since the first Zope 3.4 alpha and beta releases, we have finished the transition to a completely egg-based system. This largely means that most Zope 3 developers do not use the classic Zope 3 tar ball release anymore. However, for your convenience, the 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 package index that derives from the official Python Package Index (PyPI) and thus contains all available packages in the Python world. But for a controlled set of packages, only certain versions that are known to work together are available. The list of controlled packages and their versions for Zope 3.4 can be found at the index page [1]_. The index can be used in several ways -- described here for `buildout`-based projects. The easiest method is to specify the index option in your ``buildout.cfg`` file:: [buildout] index = http://download.zope.org/zope3.4 ... You can also "nail" the versions by downloading the versions [2]_ and insert them as follows: [buildout] versions = versions ... [versions] zope.interface 3.4.0 ... ``zopeproject`` Project Builder ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Philipp von Weitershausen has developed a package called `zopeproject` to quickly setup the boilerplate for any Zope 3 based project. Ample documentation is provided at the `zopeproject` home page [3]_. `zopeproject` uses Paste or ZDaemon to create a working server. Here are the necessary commands to get a project 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. (I hope one gets developed before Zope 3.4.0 final.) However, the ``z3c.formdemo`` package can be used as a fairly minimal setup. To get started with it, do the following:: $ svn co svn://svn.zope.org/repos/main/z3c.formdemo/tags/1.5.1 formdemo $ cd formdemo $ python bootstrap.py $ ./bin/buildout -v $ ./bin/demo fg .. [1] http://download.zope.org/zope3.4/controlled-packages.cfg .. [2] http://download.zope.org/zope3.4/versions.cfg .. [3] http://pypi.python.org/pypi/zopeproject What is 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. Downloads --------- - Zope 3.4 Egg Index: http://download.zope.org/zope3.4 - Zope 3.4 Controlled Packages: http://download.zope.org/zope3.4/controlled-packages.cfg - Zope 3.4 Latest Versions: http://download.zope.org/zope3.4/versions.cfg - The classic Zope 3 source release can be downloaded from: http://zope.org/Products/Zope3 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.4 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/zope3-users - Bug tracker at launchpad: https://launchpad.net/zope3 - IRC Channel: #zope3-dev at irc.freenode.net Acknowledgments --------------- Much thanks to everyone who contributed to this release. Since all contributions are now spread over a multitude of packages, listing all contributors is not feasible anymore.

1 0

Zope Tests: 5 OK
by Zope Tests Summarizer 05 Nov '07

05 Nov '07

Summary of messages to the zope-tests list. Period Sun Nov 4 13:00:00 2007 UTC to Mon Nov 5 13:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sun Nov 4 20:50:29 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008596.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sun Nov 4 20:52:00 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008597.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Nov 4 20:53:30 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008598.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Nov 4 20:55:00 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008599.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Nov 4 20:56:30 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008600.html

1 0

Re: [Checkins] SVN: zc.i18n/trunk/setup.py vb
by Benji York 04 Nov '07

04 Nov '07

From the check-in messages: > Changed: > U zc.i18n/trunk/setup.py > - version = '0.5.2', > + version = '0.6.0', As best I can tell, http://svn.zope.org/*checkout*/Sandbox/philikon/foundation/releasing-softwa… was accepted as policy (Jim endorsed it and no one maintained public objections). Therefore, anyone editing the trunk version numbers needs add "dev" (no hyphen) on the end. Thanks. -- Benji York Senior Software Engineer Zope Corporation

5 5