[Zope-CMF] Re: eggification status?
yuppie wrote: Wichert Akkerman wrote: A related question is: how do we want to eggify CMF? It seems to make sense to create one egg for the whole of CMF and a second egg for GenericSetup. Why not one egg for each CMF product? Can you please elaborate? *Why* one egg for each product? We'll just end up with the same egg madness that we have with Zope 3 (e.g. zope.app could've just as well stayed one big egg, IMO). It's not like the different parts of the CMF need to move at separate speeds... ___ 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
[Zope-CMF] Re: eggification status?
Philipp von Weitershausen wrote: yuppie wrote: Wichert Akkerman wrote: A related question is: how do we want to eggify CMF? It seems to make sense to create one egg for the whole of CMF and a second egg for GenericSetup. Why not one egg for each CMF product? Can you please elaborate? *Why* one egg for each product? We'll just end up with the same egg madness that we have with Zope 3 (e.g. zope.app could've just as well stayed one big egg, IMO). It's not like the different parts of the CMF need to move at separate speeds... The different parts don't need to move at different speed, but I would see separate eggs as an option to drop some parts out of the bundle again, which don't see any development at all. For example CMFUid has never quite been expected as a first class citizen of CMF, so having a separate egg for it, would allow us to not use or develop it anymore, when there's really no one interested in it. After all we are only talking about 8 eggs here and not a gazillion of them like Zope 3 has. Hanno ___ 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
[Zope-CMF] Re: eggification status?
Hi! Tres Seaver wrote: Ouch, sorry about that. I forgot I hadn't merged the change to use 'Products.GenericSetup' already. I'd rather that we moved to use 'Products.GenericSetup' and 'Products.CMFCore' everywhere, and leave the older stuff just pulling in from externals. I had a closer look at this, but I'm not 100% sure how to resolve it. Two questions: 1.) What's our new policy for version.txt? This is the content of the current files and my take on the Zope Foundation policy: GenericSetup-1.4beta in /GenericSetup/trunk GenericSetup-1.4beta in /Products.GenericSetup/trunk 1.4.0dev Zope Foundation policy? GenericSetup-1.3.2 in /GenericSetup/branches/1.3 GenericSetup-1.3.2 in /Products.GenericSetup/branches/1.3 1.3.3dev Zope Foundation policy? GenericSetup-1.3.2 in /GenericSetup/tags/1.3.2 GenericSetup-1.3.2 in /Products.GenericSetup/tags/1.3.2 1.3.2Zope Foundation policy? trunk (unreleased) in /CMF/trunk/CMFCore 2.2.0-devel in /Products.CMFCore/trunk 2.2.0dev Zope Foundation policy? CMF-2.1.0+ in /CMF/branches/2.1/CMFCore 2.1.0in /Products.CMFCore/branches/2.1 2.1.1dev Zope Foundation policy? CMF-2.1.0in /CMF/tags/2.1.0/CMFCore 2.1.0in /Products.CMFCore/tags/2.1.0 2.1.0Zope Foundation policy? 2.) /GenericSetup/trunk and /GenericSetup/branches/1.3 should be deleted, /CMF/trunk/CMFCore and /CMF/branches/2.1/CMFCore replaced by externals. Right? Any opinions? Cheers, Yuppie ___ 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
[Zope-CMF] Re: eggification status?
Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 yuppie wrote: Hi! Right now there are two versions of CMFCore and GenericSetup: Products.GenericSetup and GenericSetup Products.CMFCore and CMFCore wichert is currently working on GenericSetup/trunk, tseaver stitched today the 6 weeks old Products.GenericSetup/trunk/Products/GenericSetup into CMF/trunk/ and Products.GenericSetup/tags/1.3.2/Products/GenericSetup into CMF/branches/2.1/ Products.CMFCore seems not to be used - changes still go into CMF/*/CMFCore Can we please have *one* location for each product? Ouch, sorry about that. I forgot I hadn't merged the change to use 'Products.GenericSetup' already. I'd rather that we moved to use 'Products.GenericSetup' and 'Products.CMFCore' everywhere, and leave the older stuff just pulling in from externals. +1 - me want repoze :) Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ 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
[Zope-CMF] Re: eggification status?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 yuppie wrote: Hi! Right now there are two versions of CMFCore and GenericSetup: Products.GenericSetup and GenericSetup Products.CMFCore and CMFCore wichert is currently working on GenericSetup/trunk, tseaver stitched today the 6 weeks old Products.GenericSetup/trunk/Products/GenericSetup into CMF/trunk/ and Products.GenericSetup/tags/1.3.2/Products/GenericSetup into CMF/branches/2.1/ Products.CMFCore seems not to be used - changes still go into CMF/*/CMFCore Can we please have *one* location for each product? Ouch, sorry about that. I forgot I hadn't merged the change to use 'Products.GenericSetup' already. I'd rather that we moved to use 'Products.GenericSetup' and 'Products.CMFCore' everywhere, and leave the older stuff just pulling in from externals. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHL3Kn+gerLs4ltQ4RAi3FAKDK3drswCLhMZWLq2t9UIZH04mW0wCfTcTS RiXAV5CttE7W1CqRasmqegw= =ZsE9 -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
Re: [Zope-CMF] Re: eggification status?
Previously Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 yuppie wrote: Hi! Right now there are two versions of CMFCore and GenericSetup: Products.GenericSetup and GenericSetup Products.CMFCore and CMFCore wichert is currently working on GenericSetup/trunk, tseaver stitched today the 6 weeks old Products.GenericSetup/trunk/Products/GenericSetup into CMF/trunk/ and Products.GenericSetup/tags/1.3.2/Products/GenericSetup into CMF/branches/2.1/ Products.CMFCore seems not to be used - changes still go into CMF/*/CMFCore Can we please have *one* location for each product? Ouch, sorry about that. I forgot I hadn't merged the change to use 'Products.GenericSetup' already. I'd rather that we moved to use 'Products.GenericSetup' and 'Products.CMFCore' everywhere, and leave the older stuff just pulling in from externals. +1, especially if you can merge the changes from GS trunk into Products.GenericSetup and put a clear warning in the old location. 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
