-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 23 Feb 2007, at 09:55, Wichert Akkerman wrote:
Previously Martin Aspeli wrote:
Jens Vagelpohl wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 23 Feb 2007, at 00:39, Rocky wrote:
So... what's next?
Figuring out how to deal with existing sites that need to be
modified
on the fly somehow so they don't break completely.
Does CMF core not have any kind of migration infrastructure?
An external method to do those is easily added I suppose.
CMFCore does not have any migration infrastructure. Matter of fact it
never needed one. If any migrations were needed they were either
automatic or one-offs.
I personally dislike having to instantiate stuff like external
methods or going to some tool to run upgrade steps (which may or may
not ruin your site ;). It should be the very last resort.
After reading Phillip's book I really like Zope 3 generations, but I
have no idea if that mechanism could be used at all.
jens
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFF3rAzRAx5nvEhZLIRAuzIAJwIvpP5PjtOQYDPsFqmnaL7lnWWQwCeMWjl
hEGouy8N7qmpKm2EyZ1zcW8=
=y3PE
-----END PGP SIGNATURE-----
_______________________________________________
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
