<M
Y> M>

Tue Mar 01 2005 18:53 Criteria for evaluating specifications:

As Andrew Tannenbaum said, "The nice thing about standards is that there are so many to choose from." Apparently he followed this up by: "And if you really don't like all the standards you just have to wait another year until the one arises you are looking for."

[More]

[Comments] (5) Wed Mar 02 2005 14:50 A CMS as a pile of semi-structured data:

Paul Everitt and I have long been communicating about the role of XML in the CMS world. Recently, he posted the following blog entry and asked for my opinions per email. I started writing a mail back to him, but then I realized I have a blog now too...

[More]

Fri Mar 11 2005 14:42 Zope 3 will support XML:

Paul Everitt asks Should Zope 3 support XML?. The answer is of course, yes, it should, and, what's more, yes it will, and Infrae will be one party working on it. In fact, we've already worked on it.

[More]

Fri Mar 11 2005 19:59 Five 0.3 released!: I'm happy to announce the release of Five 0.3 today, the Zope 3 in Zope 2 integration component. This release has great new features, including edit forms and add forms based on Zope 3 schemas. See the Five website for more information, and in particular the CHANGES. Thanks to all the Five developers who made this release possible!

[Comments] (10) Thu Mar 17 2005 15:56 Fixing the Zope release process:

In this article, I will identify problems with the Zope release strategy, attribute blame, propose solutions, and offer some hope for the future.

[More]

[Comments] (2) Fri Mar 18 2005 14:56 How to delay a Zope release:

Jim Fulton, today, on the Zope-3 dev list:

Now that that the decision has been made to include Zope 3 in Zope 2.8, I'd really prefer that Zope 2.8 use X3.1 code, not X3.0 code. In general, having code shared by Zope 2 and Zope 3 will complicate deprecation, probably increasing the length of time we must keep backward-compatibility code. I'd like to try to keep the Zope 3 code used in Zope 2 and the Zope 3 code used in Zope 3 in sync as much as possible.
[More]

[Main]

Unless otherwise noted, all content licensed by Martijn Faassen
under a Creative Commons License.