There are extant app-space version-control implementations if you want to try them. They don't do the full range of things that, say, CVS does, but they aren't chopped liver either.
Sorry if is OT.DirectoryStorage allows you to designate classes that should have all their history kept indefinitely. That may not have the flexibility that you need...
I'd like ZODB and Zope to support Revisions. That is, historical copies
that do not get removed when ZODB is packed.
Does the Version mechanism contribute to this kind of functionality? I'dThe accepted wisdom is that feature like this should be implemented in the application, above zodb. This has come up a few times on zodb-dev list.
like to be able to "tag" revisions of wiki pages and other documents, and
then be able to diff them later without having to create a special kind of
product for each object type that I'd like to use revisions for.
Look for ZopeVersioning and CMFStaging. Both can be (at least) browsed at cvs.zope.org
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce