I just finished migrating the CMF and related projects from
cvs.zope.org to svn.zope.org, from CVS to Subversion. All tags and
branches have moved, unlike Zope itself there won't be some
development using CVS and some using Subversion. These are the packages:
They packages became new toplevel projects at svn.zope.org, as can be
Pending final agreement on the CMF list (or an overriding word from
the CMF Pope himself) svn.zope.org will now be the canonical location
for CMF sources. They are accessed just like Zope 2.8 and Zope trunk
as described here:
The only difference is, of course, the last element in the path.
Eveerything else works as described in the document linked above. The
packages are at...
***To all CMF developers***:
Please change your sandboxes and convert them to SVN. If you see any
problem please make it known on the CMF list as soon as possible. No
data is lost on cvs.zope.org, so if there are show-stoppers we can
always switch back to using CVS. Please **do not** commit into
cvs.zope.org or svn.zope.org until we have a "yay" or "nay" on which
repository we go forward with.
If we have agreement on using svn.zope.org a couple cleanup tasks
need to be done, such as...
- "Close off" or "freeze" the CMF projects on cvs.zope.org to either
disallow checkins or bring up big fat warnings if someone tries to.
Input and ideas on this are welcome, if it was up to me I would use
the "commitinfo" file in the CVSROOT to completely prevent updates as
the first step.
- Change any references to cvs.zope.org in the CMF code to their
- Change any references to cvs.zope.org on the project web pages,
mostly http://www.zope.org/Products/CMF, to point to the svn.zope.org
- Change any download instructions that use CVS to instructions for SVN
Zope-CMF maillist - Zope-CMF@lists.zope.org
See http://collector.zope.org/CMF for bug reports and feature requests