[Zope-CMF] tools-as-utilities, merging, releasing, etc

Jens Vagelpohl jens at dataflake.org
Wed Feb 28 11:56:01 EST 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On 28 Feb 2007, at 15:14, Rocky wrote:

> Now that I have completed the primary functionality for
> five.localsitemanager it seems to me that the CMF
> jens_tools_as_utilities branch should be ready for merging into trunk
> in anticipation of the of the next cmf 2.1 alpha/beta release.

It's ready for merging when we have a story for existing sites,  
meaning a clear migration path. I was going to do some simple testing  
closer to this weekend (busy until then) and do a simple script that  
can be run via zopectl run and document it if no one else has a  
better idea or steps up.

My assumption here is that the script needs to do two things for each  
CMF Site encountered in the ZODB:

- - create the new magic component registry

- - duplicate tool registration as done by the GS componentregistry step

Please correct me if I am wrong.

jens



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFF5bQhRAx5nvEhZLIRAgBQAKC1S7fKOl74AqbJA84nLpzOpRk++QCfeQw9
wJWJg7FRTSl+oUt0rzGIWno=
=cmjX
-----END PGP SIGNATURE-----


More information about the Zope-CMF mailing list