Re: [Zope-CMF] Re: CMF 2.1.1 release
On Dec 30, 2007, at 19:08 , Dieter Maurer wrote: Jens Vagelpohl wrote at 2007-12-29 19:03 +0100: ... - CMFCore (the foundation which may be used by itself to develop other kinds of portal software) - CMFDefault + DCWorkflow + (maybe) CMFTopic (a finished sample for a CMFCore-based portal software bundle) DCWorkflow is very valuable without CMFDefault. I would put it into CMFCore or give it its own egg. It looks like Hanno already fulfilled your wish :) jens ___ 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: CMF 2.1.1 release
On Dec 29, 2007, at 14:05 , Hanno Schlichting wrote: The maintainer role can only manage releases and files, while the Owner can add new users or delete the whole package from the cheese shop. For GenericSetup Tres should probably add at least you as a second Owner. He needs your Cheese Shop login name for that. Permission handling is done through the web interface only. Interesting, I'll talk to Tres then. The few bits of documentation that I saw linked from the cheese shop did not mention this at all. Is there better documentation out there? jens ___ 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: CMF 2.1.1 release
On Dec 29, 2007, at 18:28 , Hanno Schlichting wrote: What's the status of moving all the other parts into separate projects / folders? FWIW there hasn't been a final vote on the one-meta-egg vs. individual eggs question. For the small number of CMF parts I'm +1 for individual eggs. Yes, this is an open question. Products.CMFCore has been prepared so it could be published as its own egg. But there hasn't been a decision whether to set up individual eggs for each CMF package or just one big egg or a combination of the two solutions. I like your argument where we could use this as an opportunity to move packages like CMFUid out of the bundle/egg/tarball/whatever that people get when they get the CMF. I wouldn't mind having a division where you have... - CMFCore (the foundation which may be used by itself to develop other kinds of portal software) - CMFDefault + DCWorkflow + (maybe) CMFTopic (a finished sample for a CMFCore-based portal software bundle) - CMFUid (optional add-on) - CMFCalendar (optional add-on) - CMFActionIcons (optional add-on) jens ___ 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: CMF 2.1.1 release
On Dec 27, 2007, at 12:57 , yuppie wrote: Jens Vagelpohl wrote: The CMF 2.1 branch has seen enough fixes since CMF 2.1.0 to make a meaningful bugfix release. If there are no objections I would cut CMF 2.1.1-beta tomorrow (Friday 12/28) and a final a week later. I'm out of town from tomorrow night until 1/1, that's why I would have to do the beta either tomorrow or after 1/1. The CMF-2.1-branch is currently using the GS 1.3.2 tag, I propose to move that up to the tip of the GS 1.3 branch today, and then tagging GS 1.3.3 alongside CMF 2.1.1 final and pinning them together that way. +1 If there are no objections before this evening, I'll backport the changes mentioned here: http://mail.zope.org/pipermail/zope-cmf/2007-December/026999.html No objections from me. I should have said that right away when I read your original message. jens ___ 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
