Re: [Zope-CMF] Re: state of GenericSetup trunk and branches
On 6/22/07, Rob Miller [EMAIL PROTECTED] wrote: Well. I'd prefer to have *one* obvious and explicit solution. The failover adds extra code that needs to be maintained and makes it less obvious where the version number comes from. i agree. i was thinking since my last reply that, since the code is already in there, we could support a special value in the metadata.xml file that explicitly tells GS to use the product version for the profile version, rather than having that be the default behaviour. I think that the profile version number typically should *not* be the same as the version number. Quite often you make a release without changing anything in the profile, and profiles may be just configuration and then not have anything to do with any product version. So I'd prefer if profile versions just aren't product versions at all. But it's not a strong opinion. If it is pure registration information, why don't we extend the ZCML directive? But AFAICS data like the version number belongs to the profile itself and it might be useful to add timestamp based version numbers to exported profiles. Sounds reasonable to me. All in all, btw, these new feature to GenericSetup look bitchin', and will make truly awseome! :-) -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64 ___ 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
Re: [Zope-CMF] Re: state of GenericSetup trunk and branches
The new GS looks very nice, but from the ZMI UI I can no longer see how I can import only selected steps of an extension profile. I hope that is still possible; it can be extremely useful. It looks like the import and export tab only act on the base profiels now. Wichert. -- Wichert Akkerman [EMAIL PROTECTED]It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ 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
Re: [Zope-CMF] Re: state of GenericSetup trunk and branches
Previously yuppie wrote: - How are profile dependencies specified, where are they used? http://theploneblog.org/blog/archive/2007/06/21/genericsetup-improvements suggests they are not implemented. Wichert. -- Wichert Akkerman [EMAIL PROTECTED]It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ 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
Re: [Zope-CMF] Re: state of GenericSetup trunk and branches
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 20 Jun 2007, at 06:59, Rob Miller wrote: Jens Vagelpohl wrote: Tres reminded me that we should have a real branch and release tags for GenericSetup to match up with the CMF 2.1-branch and the releases. I need to determine the current state: Has the BBQ Sprint branch at http://svn.zope.org/GenericSetup/ branches/tseaver-bbq_sprint/ ever been merged into the trunk, or is this nothing to worry about? okay, i've finally gotten around to finishing the test coverage of the new setup tool code on this branch, and it's ready to be merged to the trunk. is now a good time for this to land, or should i wait for a branch to be cut? I was hoping for 1.5 to have these changes included, otherwise I would have cut the branch and tagged a release 10 days ago when I brought this up ;) Just merge and I'll take it from there. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFGeMrjRAx5nvEhZLIRAs5xAKC7TehxEreUqQ83uDh6vDHFnMaZCwCeOGsY eBtp01NPELK7LM7nse8BXEg= =3drc -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
