The procedures for the development and maintenance of official Zope documentation nears completion.

The opinions expressed in Zope Weekly news are solely the authors', and not the opinions of Digital Creations, The Zope Community at-large, or the Spanish Inquisition.

If you or your company are doing something cool with zope, submit it to the Zope Weekly News for possible inclusion.

And Now For Something Completely Different:

Zope Status

by Brian Lloyd

Summary

A problematic 2.2.3 release and a 2.2.4 beta

Recent News

Friday the 16th we finally got a 2.2.3 release out the door. Unfortunately, it turned out that one fix activated a latent bug that prevented permissions from being acquired properly :(

Thanks to Seb who sent me an email almost immediately on that, we put that release on hold before inconveniencing too many folks. The current Zope CVS (the line for the next feature release) contains the beginnings of some test infrastructure for the Zope core. While its not mature enough yet, I hope to use this in the future to build a regression test rig to help catch this sort of thing. In the meantime, we'll plan to do a (short) beta for third-dot releases. While not perfect, that will at least give us more coverage and sanity-checking than we can achieve in house. Monday saw 2.2.4b1 released, which includes the 2.2.3 fixes plus the fix for the activated bug.

In other news this week, Michel Pellatier has created a proposal for a Zope API Reference:

http://dev.zope.org/Wikis/DevSite/Proposals/APIReference

Toby Dickenson's Python 2.0 Migration proposal has been seeing some comments:

http://dev.zope.org/Wikis/DevSite/Proposals/Python20Migration

Ken Manheimer is working on the "Wiki For Now" proposal (or "Wiki Aspirin" as Jim calls it) that aims to provide solutions for some of the more painful shortcomings of Wikis as they are used for running development projects. This one is on the fast track, so get your licks in now:

http://dev.zope.org/Wikis/DevSite/Proposals/WikiForNow

Near Future

I am still on the hook to implement changes to dev.zope.org to make it easier to deal with the growing number of artifacts there. That is still on the to-do list, though it is currently out-prioritized by an Extra- Special Project. More info on that coming soon!

Documentation

by Michel Pelletier

Greetings. This a quiet week of use cases, phone meetings, and proposal writing. If you're interested, please check out and comment on these hot news items!

• The Documentation Process
• API Reference proposal
• Is Pink Turkey Meat Safe?
• The new Zope release, 2.2.4, contains the new DTML reference! This will also be an appendix in The Book.
• The Book has gone to the editors for a second round of technical review! After some internal review, they will relese it to the community reviewers. We know it's taking a while, please bear with us (them). You know we love you.

Zope Web

-- by Andrew Sawyers

Zope.org Update?

I'm new to the DC team and will be working with Ethan to bring Zope.org online on the new clusters. We're still experiencing some resource issues with the current Zope.org system, but next week should see a smooth transition to the cluster and improved performance for the Zope.org site. Ethan and I are discussing many new things to improve the Zope.org site, so stay tuned as we work these out and announce them here.

-EOT-