Re: [Zope-CMF] CMFSetup comments
On Apr 4, 2005, at 15:22, Chris Withers wrote: Sidnei da Silva wrote: Look for CMFSetupExtensions on the collective. Why am I not suprised... Why couldn't this just have been fed into the real CMFSetup?! +1 for extending CMFSetup instead of functionality in all kinds of strange places. Oh well, I'm not all that surprised, either. 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
[Zope-CMF] CMF 1.5.1 release schedule
Just as a heads-up: I would like to release a second beta (1.5.1beta2) this coming weekend. If no serious bugs are found, the final version (to be released 1-2 weeks later) should not be much different from the beta. To help this process, once 1.5.1beta2 is out I would like to restrict checkins to the CMF-1_5-branch until the final CMF 1.5.1 version is released. Only serious bugs or bugs uncovered as part of the beta cycle should be checked in between 1.5.1beta2 and 1.5.1 final. Once 1.5.1 final is out the "normal" rules apply, meaning "no big feature changes on the maintenance branch" and "need to be fully backwards compatible across minor releases". Just as Andreas has done with Zope itself, I want to champion a more ordered and timely release schedule. This implies that no one will have to scramble getting their favorite bug fixes into the CMF before a release because it was never clear when the next release came. Action item for the active developers: Please comment if you see a problem with this schedule or the changed release philosophy. 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
[Zope-CMF] Re: CMF 1.5.1 release schedule
On Apr 10, 2005, at 14:44, Tres Seaver wrote: +1. I don't see this som mach as a changed philosophy as a restart of release managment. You're right - that's a better description. No pun on any prior release management activities intended. 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
[Zope-CMF] Re: CMF 1.5.1 release schedule
On Apr 11, 2005, at 10:07, yuppie wrote: But just to make it explicit: For CMFSetup the "normal" rules are not suitable. CMFSetup is not as mature as the other packages and we still have to change it in fundamental ways. Though these changes might not always be fully backwards compatible, I believe we should keep merging them into the CMF-1_5-branch. Yeah, that's fine as long as the 1.5.1 release doesn't end up with something broken. We're only talking a 7-10 day time span, anyway. 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] CMF 1.5.1 release schedule
On Apr 11, 2005, at 21:41, Gregoire Weber wrote: There are two points open I'd like to address: - CMFUid needs an algorithm generating uids correctly: I've collected the suggestions from the list (either a simple counter or something a little more elaborated) - Florent criticized once that th OpaqueItem stuff loops over all attributes of an object on copy/move/delete operations: Instead of checking *all* attributes for the ``ICallableOpaqueItem`` interface I'd like to just check for attributes registered in a property of CMFDefault's PropertyTool. I'll do these changes. If somebody wants to help it is ok also. Thanks Gregoire, any help is appreciated. Jens, may I do them also after the beta2? Please remember that releases will come a bit faster now. You won't lose much by applying changes after 1.5.1 final, I promise. I'm willing to delay 1.5.1beta2 by a few days if that works better for you, but I really don't want anything beyond urgent bug fixes in the one week between 1.5.1beta2 and 1.5.1 final. The 1.5 branch is nice and stable at this point, let's not risk that by feeling rushed to get something in before 1.5.1. 1.5.2 won't be too far away. 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] [dev] anybody using TypesTool._checkViewType?
On Apr 12, 2005, at 12:33, yuppie wrote: Hi! TypesTool._checkViewType was added for a feature that never worked, see: http://www.zope.org/Collectors/CMF/114 So unless someone invented an other use case for it, it's just cruft. If there are no objections, I'd like to remove it before CMF 1.5.1b2 is released. +1 Just for shits and giggles I grepped Plone (2.1) and a bunch of Plone-related products, they don't seem to use that code. 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] [dev] anybody using portal_workflow.getActionsFor or WorkflowInformation?
On Apr 12, 2005, at 13:33, yuppie wrote: Hi! AFAICS ActionProvider.listActionInfos makes portal_workflow.getActionsFor obsolete. And WorkflowInformation is just used by getActionsFor. So I'd like to add a deprecation warning on the Zope-2_7-branch and to remove them on HEAD/CMF 1.6. (Or in CMF 1.7, if some people are actually using them.) Any objections? I think we should stick with the "removal comes two dot-releases after deprecation" policy that Jim set up at some point for Zope itself. I would deprecate on the 1.5 branch and HEAD and remove in 1.7. 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] Why doesn't Filesystem Directory View support .metadata on folders?
On Apr 13, 2005, at 18:45, sureshvv wrote: Is there a reason for this? Would you be interested in a patch? It does. Look at CMF CVS HEAD. 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] CMF 1.5.1 release schedule
On Apr 14, 2005, at 9:18, Gregoire Weber wrote: Hi Jens, I try hard to get the uid generation part right before the beta. If a delaying will help others also it would be nice to delay the beta for a few days. If it's only for my part it's optional as I can't guarantee it'll help me. I'll send you an e-mail when I started fix my issues with a time frame. Just make sure to drop me an email before Saturday evening, otherwise I'll cut the beta Sunday morning. If we delay the beta I want to put a limit on this delay, it should be out by Wednesday at the latest. 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
[Zope-CMF] Expression context naming scheme - redux
A few weeks ago I did a little bit of cleanup to standardize the expression context naming schema used for the bound variables in the different expession context situations used around the CMF: http://www.zope.org/Collectors/CMF/328 Back then I left out DCWorkflow because even though it is the standard workflow for CMF now it is still somewhat "standalone" and always used a more Zope-like naming scheme. Specifically, it uses "here" where the CMF now standardizes on "object": http://www.zope.org/Collectors/CMF/338 I am proposing to add a simple alias from "here" to "object" in the DCWorkflow expression context. Unlike the rest of CMF I don't want to call "here" deprecated, but at least introduce more consistency. If no one objects I'll put that in before 1.5.1beta2 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: setSecurityProfile
On Apr 15, 2005, at 19:29, Florent Guillaume wrote: yuppie <[EMAIL PROTECTED]> wrote: Florent Guillaume wrote: I'll be changing MemberData.setSecurityProfile to use user._doChangeUser() instead of hitting the attributes directly, if nobody sees a problem with that. Why not userFolderEditUser()? I checked this in (for 1.5 and HEAD). As usual unit tests took the longest time, MemberData is hardly tested at all :( Thanks Florent! Actually, MemberData is kind of a weird subject. Its interactions with the underlying user folder are a little odd and lack clear policy. Some things are written out to the user folder, others stay in the wrapper. Most things are looked up in the wrapper and sometimes create inconsistencies with the actual user database if it gets updated without the CMF knowing. Maybe I could try and think of an extension that allows you to specify what gets written where (and looked up where), some simple ZMI UI on the MemberDataTool. Anyone have any thoughts on that? 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] CMF 1.5.1 release schedule
On Apr 16, 2005, at 11:22, Gregoire Weber wrote: Hi Jens, just go on with the release if you don't hear anything from me today and tomorrow. What's the expected date of a 1.5.2 release? Hi Gregoire, With 1.5.1beta2 tomorrow 1.5.1 final will be scheduled for one week later, meaning Sunday April 24. The 1.5.2 schedule hasn't been set, but in my opinion a first beta should be no later than 2 months from now. 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
[Zope-CMF] CMF 1.5.1beta2 Released
Zope Corporation is pleased to announce the release of version 1.5.1beta2 of the Zope Content Management Framework (CMF). This release is intended for testing purposes only; we do not recommend deploying it to production servers. The final release of version 1.5.1 is expected on the weekend of April 24, 2005. What is the CMF? The Zope Content Management Framework provides a set of services and content objects useful for building highly dynamic, content-oriented portal sites. As packaged, the CMF generates a site much like the Zope.org site. The CMF is intended to be easily customizable, in terms of both the types of content used and the policies and services it provides. Where do I get it? Download it from http://zope.org/Products/CMF/CMF-1.5.1beta2 Points of interest include: - "Windows ZIP file", http://zope.org/Products/CMF/CMF-1.5.1beta2/CMF-1.5.1beta2.zip - "Unix tar/gzip archive", http://zope.org/Products/CMF/CMF-1.5.1beta2/CMF-1.5.1beta2.tar.gz - "Release notes", http://zope.org/Products/CMF/CMF-1.5.1beta2/README.txt - "Change history", http://zope.org/Products/CMF/CMF-1.5.1beta2/CHANGES.txt - "Installation instructions", http://zope.org/Products/CMF/CMF-1.5.1beta2/INSTALL.txt Where do I go to learn more? The "CMF mailing list":mailto:[EMAIL PROTECTED] has many participants who are active in supporting the CMF. ...to report bugs? The "CMF Collector":http://zope.org/Collectors/CMF is ths place to report bugs (please search for existing reports of your issue first!) ___ 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] Where can I found information about CMFCore class DirectoryRegistry ?
On Apr 21, 2005, at 2:52, KLEIN Stéphane wrote: Hello, I search information about CMFCore class DirectoryRegistry. What is it ? How use it ? ... Where can I found information about it ? DirectoryRegistry is mostly an internal implementation detail and thus not part of any published API. You will have to read the code. 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: Where can I found information about CMFCore class DirectoryRegistry ?
On Apr 21, 2005, at 3:03, KLEIN Stéphane wrote: Jens Vagelpohl a écrit : On Apr 21, 2005, at 2:52, KLEIN Stéphane wrote: Hello, I search information about CMFCore class DirectoryRegistry. What is it ? How use it ? ... Where can I found information about it ? DirectoryRegistry is mostly an internal implementation detail and thus not part of any published API. You will have to read the code. jens Yes, but it's used to build product then it's part of interface. Isn't it ? What I mean is that it's not made to be used directly from application code. So no, it is not part of the interface. 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] Expression context naming scheme - redux
On Apr 21, 2005, at 14:55, Chris Withers wrote: Jens Vagelpohl wrote: I am proposing to add a simple alias from "here" to "object" in the DCWorkflow expression context. Unlike the rest of CMF I don't want to call "here" deprecated, but at least introduce more consistency. Sort of semi-seriously, why isn't "context" used everywhere? Please take the time to read the original thread when I did the first pass. 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: Where can I found information about CMFCore class DirectoryRegistry ?
On Apr 21, 2005, at 21:31, KLEIN Stéphane wrote: Chris Withers a écrit : Well, the source code is it. You don't need to worry about any of these though, if you just want to change and add some fields.. My new CMF Event is a copy of standard CMF Event. My personnal product don't contain a CMF Calendar, then I must drop it in "__init__.py". I would like understand why I do. Again, these are not all documented because they are internal details that do not belong in the public API. You will have to read the code, there is no way around it, sorry. 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
[Zope-CMF] Re: [CMF-checkins] CVS: CMF - CHANGES.txt:1.248.2.92
On Apr 22, 2005, at 19:05, Julien Anguenot wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 oups didn't see it was a feature freeze time.. Do you want me to rollback this optim on the 1.5-branch ? (it's also on HEAD) Hi Julien, If you could roll it back on the CMF-1_5-branch, that's great. I promise I will release CMF 1.5.1 final on Sunday, then the branch is free for (backwards-compatible) changes again. Thanks! 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-checkins] CVS: CMF - CHANGES.txt:1.248.2.92
On Apr 22, 2005, at 19:04, Florent Guillaume wrote: Jens Vagelpohl <[EMAIL PROTECTED]> wrote: Why is all this stuff checked in just before the final? This is not a bug fix, just like the previous checkin. I had specifically asked to refrain from non-bugfix checkins before the final this Sunday... Agreed, Julien will revert. Note, I want to checkin a "bugfix" in a few hours to enable some LOG in reindexObjectSecurity if there's problems during the getObject. The sooner it's here, the better we'll find problems with Zope 2.8 and buggy code. Unless you object, of course. No objection from me, that's a good idea since we have had this whole row about getObject. Speaking about Zope 2.8, can I close the outstanding issue about CMF-1_4-branch not working on Zope 2.8? 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
[Zope-CMF] Re: [CMF-checkins] CVS: CMF - CHANGES.txt:1.248.2.92
Why is all this stuff checked in just before the final? This is not a bug fix, just like the previous checkin. I had specifically asked to refrain from non-bugfix checkins before the final this Sunday... jens On Apr 22, 2005, at 18:52, Julien Anguenot wrote: Update of /cvs-repository/CMF In directory cvs.zope.org:/tmp/cvs-serv11784 Modified Files: Tag: CMF-1_5-branch CHANGES.txt Log Message: Update === CMF/CHANGES.txt 1.248.2.91 => 1.248.2.92 === --- CMF/CHANGES.txt:1.248.2.91 Fri Apr 22 12:27:11 2005 +++ CMF/CHANGES.txt Fri Apr 22 12:52:23 2005 @@ -8,6 +8,11 @@ - CMFCatalogAware: reindexObjectSecurity() optimizations in case of an indexable container. + +- reindexObjectSecurity() supports now an optional argument + skip_self that prevent the object itself to be reindexed but its + descendants only. Optimization issue when you want to reindex + all the idxs *and* the security in a single shoot with reindexObject() CMF-1.5.1beta2 (2005/04/17) ___ CMF-checkins mailing list CMF-checkins@zope.org http://mail.zope.org/mailman/listinfo/cmf-checkins --- Jens Vagelpohl [EMAIL PROTECTED] Zetwork GmbHhttp://www.zetwork.com/ ___ 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] CMF 1.5.1 Released
Zope Corporation is pleased to announce the release of version 1.5.1 of the Zope Content Management Framework (CMF). This release marks the latest stable release in the CMF 1.5 series and should be suitable for production use. What is the CMF? The Zope Content Management Framework provides a set of services and content objects useful for building highly dynamic, content-oriented portal sites. As packaged, the CMF generates a site much like the Zope.org site. The CMF is intended to be easily customizable, in terms of both the types of content used and the policies and services it provides. Where do I get it? Download it from http://zope.org/Products/CMF/CMF-1.5.1 Points of interest include: - "Windows ZIP file", http://zope.org/Products/CMF/CMF-1.5.1/CMF-1.5.1.zip - "Unix tar/gzip archive", http://zope.org/Products/CMF/CMF-1.5.1/CMF-1.5.1.tar.gz - "Release notes", http://zope.org/Products/CMF/CMF-1.5.1/README.txt - "Change history", http://zope.org/Products/CMF/CMF-1.5.1/CHANGES.txt - "Installation instructions", http://zope.org/Products/CMF/CMF-1.5.1/INSTALL.txt Where do I go to learn more? The "CMF mailing list":mailto:[EMAIL PROTECTED] has many participants who are active in supporting the CMF. ...to report bugs? The "CMF Collector":http://zope.org/Collectors/CMF is ths place to report bugs (please search for existing reports of your issue first!) ___ 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] CMF 1.4 + Zope 2.8
On Apr 25, 2005, at 15:30, Andreas Jung wrote: --On Montag, 25. April 2005 15:27 Uhr +0200 Florent Guillaume <[EMAIL PROTECTED]> wrote: Jens Vagelpohl <[EMAIL PROTECTED]> wrote: Speaking about Zope 2.8, can I close the outstanding issue about CMF-1_4-branch not working on Zope 2.8? I don't know, I've never used those two together (and I'm not sure we should support it). Hopefully CMF 1.5 will work with Zope 2.8?! Every software has its time...and the time of CMF 1.4 is nearly over :-) Well, tell that to the Plone folks. Actually, IMHO I don't see the sense in trying to make it run. The only holdout I know, Plone, has always been slow to recommend/ship new versions of underlying software. So I don't see how they can plan on Zope 2.8, seeing how glacial the progress away from CMF 1.4 is... 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: Where can I found information about CMFCore class DirectoryRegistry ?
On May 3, 2005, at 8:47 , sureshvv wrote: KLEIN Stéphane wrote: Hello, I search information about CMFCore class DirectoryRegistry. What is it ? How use it ? ... Where can I found information about it ? Thanks for your help, Since you don't seem to be getting much help, here is what I know. He has gotten help. The help is "don't use DirectoryRegistry directly". Anything else has the potential of blowing up right in his face because it is not part of the public API and thus prone to unexpected changes. 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] Subversion?
On May 3, 2005, at 4:28 , Florent Guillaume wrote: How about migrating CMF to subversion too? I'd say, 1.5 and HEAD. To be honest, I don't see the point in that. -1 from me. 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] Subversion?
On May 4, 2005, at 11:09 , Stefan H. Holek wrote: +1 here Once you start working with svn you will quickly realize how annoying cvs can be, Jens ;-) That's the argumentation I don't like. "It's better" means nothing to me. You need to keep in mind that there are two groups of people affected negatively: - those who have no problem working with CVS who are now forced into SVN, possibly for no good technical/rational reason - those who have to spend the time doing actual migration from a CVS to a SVN repo I personally would think that better reasons need to be mentioned. Good technical reasons. So, still -1 from me. 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] Subversion?
On May 4, 2005, at 3:44 , Florent Guillaume wrote: Well it would make things homogenous with the rest of Zope and Zope-related projects. And you could do checkouts of Zope + CMF or Plone + CMF or CPS + CMF with only a few well placed svn:externals in one command. You're slightly contradicting yourself here. It's not "the rest of Zope and Zope-related products" that are on SVN. It's only Zope 2.8+, Plone stuff and CPS. I would claim the opposite and say that most Zope-related products are still on CVS, and a few large ones (especially Plone/Plone-related products and CPS) are on SVN. And frankly merging and cheap branches and having diff -r PREV:BASE makes svn much nicer to use day to day. Haven't had any problem doing branches and diffing in CVS, that's a purely subjective observation. The cvs2svn script is quite mature, migrating is not difficult in itself, and ZC has already done it for Zope. That's unrelated to my original opinion, really. Don't get me wrong here, I'm not trying to diss anyone, it's just that I haven't seen many "valid" arguments for such a move that really benefit most active developers. At least for Zope itself there were a couple good arguments if I remember correctly, but they had to do with Zope repository specifics (stitching in unrelated stuff etc). Now, if there was zero cost to switching, fine. I can deal with having to get further into SVN. But there is a cost, especially for those people who do the repository migration and then presumably cleanup. You're "force-volunteering" people at ZC right now to do that work. They should have the final word, if anyone. 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] Subversion?
On May 4, 2005, at 3:54 , Chris McDonough wrote: - bdb tends to need recovery from time to time and I'm not sure of the feasibility of filesystem-based Subversion repos, and CVS really doesn't have this issue. That's one of the biggest reasons why I would not want to be involved in administering a SVN setup. CVS requires nearly no management for small projects like CMF, except for software upgrades once in a while. And those can be automated. - If we put something in Subversion and keep something in CVS, merging becomes a chore. All of the code should really be in one or the other. The current state of the world wrt to Zope 2.7 in CVS and 2.8/HEAD in Subversion is a real pain. If we move I would also argue for a complete move. 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] Subversion?
On May 5, 2005, at 6:17 , Florent Guillaume wrote: You're "force-volunteering" people at ZC right now to do that work. They should have the final word, if anyone. I don't see how I could force-volunteer someone at ZC. I'm trying to see if people would be interested, and stress point why they should. ZC will have the final word in any case. You are force-volunteering someone there because they own/administer the machines, so it will most likely be someone from ZC who is doing the actual work... (well yes, people can volunteer, but there's a legitimate interest at ZC to keep the number of people who have fully privileged shell access on those boxes small) 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
[Zope-CMF] Re: CVS: Products/CMFCore - PortalContent.py:1.47.2.1
On May 8, 2005, at 18:28, yuppie wrote: - CMFTopic.Topic/CMFCore.PortalContent: Both these classes were using the now-deprecated CMFCore.utils._getViewFor method, and strangely enough the deprecation warning didn't show. Replaced with the new method of getting the view. Maybe the deprecation warning didn't show up because the method was never called? Yes, I think that's right. I believe DynamicType __before_publishing_traverse__ catches all those calls under normal circumstances, which is something that occurred to me after the fact. 1.) It implements different behavior than CMF HEAD 2.) It breaks backwards compatibility I propose to use the code from HEAD and the _getViewFor code as fallback in case no '(Default)' alias is defined. Yes, it's true. I didn't even look at CVS HEAD, I applied a "recipe" I had used for a different CMF-based software product a little while ago. I'll clean it up over the next couple days. 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: CVS: Products/CMFCore - PortalContent.py:1.47.2.1
On May 8, 2005, at 23:58, Jens Vagelpohl wrote: 1.) It implements different behavior than CMF HEAD 2.) It breaks backwards compatibility I propose to use the code from HEAD and the _getViewFor code as fallback in case no '(Default)' alias is defined. Yes, it's true. I didn't even look at CVS HEAD, I applied a "recipe" I had used for a different CMF-based software product a little while ago. I'll clean it up over the next couple days. OK, cleanup done. Works like CVS HEAD and falls back to utils._getViewFor in case there is a problem. 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 1.4 + Zope 2.8
On May 11, 2005, at 20:08, Christian Heimes wrote: Jens Vagelpohl wrote: Hopefully CMF 1.5 will work with Zope 2.8?! Every software has its time...and the time of CMF 1.4 is nearly over :-) Well, tell that to the Plone folks. Actually, IMHO I don't see the sense in trying to make it run. The only holdout I know, Plone, has always been slow to recommend/ship new versions of underlying software. So I don't see how they can plan on Zope 2.8, seeing how glacial the progress away from CMF 1.4 is... I thought you and Whit were working on the CMF 1.5 fixes for Plone 2.1? How far are you? We had a discussion on #plone about Plone 2.2. We might focus Plone 2.2 on new releases of CMF, Zope2+Five and optimizations like Five/ Zope3 based views. Not far. I'm in the middle of moving for a contracting position right now. I also felt that it was useless because the decision to continue with CMF 1.4 had been made at some point. No one has told me anything about specific plans as far as newer CMF versions go. I'm glad to help but I perceived a distinct lack of enthusiasm/ support from the Plone side. I might be wrong. 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: CMFHotfixes in the repository
On 3 Jun 2005, at 18:36, Tres Seaver wrote: Have the CMFHotfix_* products been recently moved into the CMF repository? Nope, they have been there all along. As with some of the other productgs (CMFStaging, CMFWorkspaces, at least), they are unde '/CMF' for "hysterical raisins", and could probably be moved into another location. How about having a toplevel "CMF" package as we do right now and add a second toplevel package, maybe naming it "CMFAddons" (better suggestions welcome) as the place for all those bits that are not part of the standard CMF package? Then I would just do a physical move on the filesystem on cvs.zope.org to get those hotfixes etc in 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
[Zope-CMF] CMF 1.5.2
Question to the group: Any problem with starting the CMF 1.5.2 beta cycle this week or next week? 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] CMF 1.5.2
On 13 Jun 2005, at 15:59, Florent Guillaume wrote: Jens Vagelpohl <[EMAIL PROTECTED]> wrote: Question to the group: Any problem with starting the CMF 1.5.2 beta cycle this week or next week? No problem, however I'll still be checking in changes to CMFSetup in the next few days. Don't worry, this was more of a "let's cut a beta in the next 1-2 weeks" thing. If no one yells until the end of this week I will create a tag some time next week. 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] Adding context to FactoryTypeInformation.queryMethodID
On 13 Jun 2005, at 20:04, Christian Heimes wrote: For the new feature I need the caller context in queryMethodID for a dynamic view template. I propose to alter the method from queryMethodID(self, alias, default=None) to queryMethodID(self, alias, default=None, context=None) and add context=self to all calls of queryMethodID. Hm... On the surface it looks backwards compatible to me and low- risk. Yuppie did most of that code if I remember correctly, he might want to speak up. I have to admit I don't know much about the origins and intents reflected in those bits beyond reading the naked code. 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] CMF-head and Zope 2.8
On 14 Jun 2005, at 21:11, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I would like to update the head of CMF to reflect a dependency on Zope 2.8+. In particular, I want to reset any 'import Zope' to 'import Zope2', and begin looking at using Five more directly, without worrying about testing for its absence. The CMF 1.5 branch will thus be the EOL for sites which chose to continue running Zope 2.7.x. +1 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: Adding context to FactoryTypeInformation.queryMethodID
On 17 Jun 2005, at 20:46, Christian Heimes wrote: yuppie wrote: But AFAICS it doesn't make much sense for the CMF to duplicate a feature that Zope 2.8/Five provides already. You are right but we can't use new Zope 2.8 features at the moment. It would delay Plone 2.1 and introduce new dependencies. I sense a disconnect between different Plone factions here. How does your statement jive with Alan Runyan's newfound interest (and Stefan Holek's concurrence) in making sure Plone 2.1 is compatible with both CMF 1.5 and Zope 2.8? 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: Conflict between PortalFolder and CMFBTreeFolder
On 20 Jun 2005, at 09:24, Christian Heimes wrote: yuppie wrote: > First of all CMF 1.5.2 has to be backwards compatible to CMF 1.5.0 and > 1.5.1, so reverting that change is no option. That is understandable from your point of view but I don't agree with the desicion. The new ordered PortalFolder has deep impacts on software that exists for years and depend on PortalFolder to be a subclass of Folder w/o order support. This includes BTreeFolder2, Archetypes and all Archetypes based products. Archetypes distinguishes explictly between BaseFolder and OrderedBaseFolder. On a general note, if this is so important I am puzzled that this is coming up now and not *months* ago. CMF 1.5.0 has been released ages ago. Beta testing periods are the time to find and solve these problems, not the middle of the maintenance release cycle... 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: Conflict between PortalFolder and CMFBTreeFolder
On 20 Jun 2005, at 10:56, yuppie wrote: The downside is that software written for CMF 1.5 has to be altered. But it is much easier to alter a few lines in some products than trying to get rid of the ordered stuff in PortalFolder. That's not fair. You are free to ignore CMF development for years, but you can't make other people pay for that. Upgrading from 1.5.x to the latest 1.5 version has to work without *any* trouble. I support that statement. In my opinion it is unacceptable to make this change on the CMF 1.5 branch at this point. If there is a problem, please change the software that relies on the old behavior instead. 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: Conflict between PortalFolder and CMFBTreeFolder
On 20 Jun 2005, at 18:22, Tres Seaver wrote: Yvo, Jens, Florent: you were the last ones to chime on on the "CMF 1.5.2" thread; would that work for you, assuming we merge Christian's patch? I can tag at any point in time. 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
[Zope-CMF] CMF 1.5.2beta released
Zope Corporation is pleased to announce the release of version 1.5.2beta of the Zope Content Management Framework (CMF). This release is intended for testing purposes only; we do not recommend deploying it to production servers. The final release of version 1.5.2 is expected mid-July 2005. What is the CMF? The Zope Content Management Framework provides a set of services and content objects useful for building highly dynamic, content-oriented portal sites. As packaged, the CMF generates a site much like the Zope.org site. The CMF is intended to be easily customizable, in terms of both the types of content used and the policies and services it provides. Where do I get it? Download it from http://zope.org/Products/CMF/CMF-1.5.2beta Points of interest include: - "Windows ZIP file", http://zope.org/Products/CMF/CMF-1.5.2beta/CMF-1.5.2beta.zip - "Unix tar/gzip archive", http://zope.org/Products/CMF/CMF-1.5.2beta/CMF-1.5.2beta.tar.gz . - "Release notes", http://zope.org/Products/CMF/CMF-1.5.2beta/README.txt - "Change history", http://zope.org/Products/CMF/CMF-1.5.2beta/CHANGES.txt - "Installation instructions", http://zope.org/Products/CMF/CMF-1.5.2beta/INSTALL.txt Where do I go to learn more? The CMF mailing list ([EMAIL PROTECTED]) has many participants who are active in supporting the CMF. ...to report bugs? The "CMF Collector":http://zope.org/Collectors/CMF is the place to report bugs (please search for existing reports of your issue first!) ___ 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] Moving to CMF 1.5.2
Hi guys, As you have noticed, I have just released 1.5.2beta. Tres tagged it a couple days ago and I just published it from that tag. Since he is at Europython right now I'm assuming he had enough of the cats that need herding for a release on hand to get a consensus that the time is ripe for this beta. As always, the beta implies that you should hold off with anything but bugfixes on the CMF-1_5-branch in CVS until CMF 1.5.2 final is released. If nothing comes up, I would actually like to do that in 1-1.5 weeks without a second beta, but if fixes creep in a second beta will be released instead. The latest point at which CMF 1.5.2 will come out is the middle of July, a little over 2 weeks from now. Please test this beta and report any severe bugs that must be fixed before 1.5.2 final. 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
[Zope-CMF] Re: Moving to CMF 1.5.2
On 28 Jun 2005, at 11:25, yuppie wrote: Well. I don't consider this a release candidate. There are still issues with Zope 2.8.0 compatibility. Some of them are resolved on the Zope-2_8-branch, but I think we should try to make CMF 1.5.2 work with Zope 2.8.0: At this point the policy is very simple: - releases are timed - if you feel something must make it into the next release it is up to you to mobilize either yourself or someone else to make it happen within the release schedule. There aren't any specific "goals" for these third-dot-releases per se, including an explicit goal that "CMF 1.5.2 must work with Zope 2.8". It is desirable, yes, but won't hold up a final release until someone finds it urgent enough to do something about it. Remember, there is always the next third-dot-release... Can't speak for Florent and what he has or hasn't done. Same policy applies. If someone finds an issue urgent enough... etc. 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: Moving to CMF 1.5.2
On 28 Jun 2005, at 13:13, Florent Guillaume wrote: yuppie <[EMAIL PROTECTED]> wrote: Besides that, I'm a bit confused by the fact that Florent didn't backport his latest CMFSetup changes to the CMF-1_5-branch. Yeah I was waiting to see if I had more changes to do on HEAD before backporting everything at once. I think I'll just backport them today or tomorrow if people think it's ok (again, CMFSetup is a bit of a special case). Yes please do. As far as I know the Plone guys are very interested in its rapid development as well. 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
[Zope-CMF] Re: Moving to CMF 1.5.2
On 29 Jun 2005, at 08:29, Christian Heimes wrote: I made Plone 2.1 working with CMF 1.5 and 2.8 and I finally got the people convinced to move to the new versions. We need a version of CMF that works with the next version of Zope 2.8 (2.8.1). From that statement it follows that CMF 1.5 must be working with Zope 2.8 because you've been running them together successfully? I am willing to cut a release closer to the end of the month if you (this is a call to action for you since at this point you have the most knowledge about what Plone 2.1 needs) can submit a list of items that are critical for Plone 2.1 and CMF 1.5.2 final to the CMF list so we can decide who does what. 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: Moving to CMF 1.5.2
On 1 Jul 2005, at 14:26, Florent Guillaume wrote: That's now merged (genericizing of TypeInfo export). But boy that was painful! I really wish we moved to svn... To be honest, I would like a move to SVN myself. I would even volunteer to do it. I've been using it for a while now and I learned to like it a lot. (ChrisW, stop snickering now!) 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: Moving to CMF 1.5.2
On 2 Jul 2005, at 15:45, Tres Seaver wrote: To be honest, I would like a move to SVN myself. I would even volunteer to do it. I've been using it for a while now and I learned to like it a lot. I'm fine with the move, as long as it is the "preserve all history" one; I don't want to have to go back to CVS for "old" stuff. Yes, I would use that migration script that comes with SVN which claims to retain all history. Tomorrow, time permitting, I might make a copy of the CMF tree inside the CVS repository and run the migration script against it. I want to product a test-migrated instance in svn.zope.org that we can all look at to see if this will work. (ChrisW, stop snickering now!) I hear snickers are the least of the audio feedback emanationg from y'alls end of the cubical space. ;) You're right, most of the time it is the sound of gnashing teeth and a lot of cursing at the spaghetti code from a certain software package ;) 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: Moving to CMF 1.5.2
Since the list of issues has already shrunk a lot this last week I propose cutting the (final) beta shortly after this coming weekend (I'll be in Edinburgh that weekend, otherwise I'd suggest the weekend). Any good reason not to do CMF 1.5.2beta2 on Monday, June 11? Speak up now or forever hold your peace... 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
[Zope-CMF] Moving CMF into subversion (was: Moving to CMF 1.5.2)
On 3 Jul 2005, at 23:19, Jens Vagelpohl wrote: Yes, I would use that migration script that comes with SVN which claims to retain all history. Tomorrow, time permitting, I might make a copy of the CMF tree inside the CVS repository and run the migration script against it. I want to product a test-migrated instance in svn.zope.org that we can all look at to see if this will work. So I've played around with cvs2svn in a sandbox that contains a copy of the cvs.zope.org CVSROOT and the /CMF folder but I'm running into a problem. Back when the original Zope migration happened the script would create a hierarchy like this, which is the hierarchy used for all projects on svn.zope.org and I'd like to stick to that: /repository/projectname/[trunk|tags|branches] With version 1.2.1 of the cvs2svn package (and with an unknown older version that I found in Jim's home directory on cvs.zope.org) I can only produce this kind of hierarchy: /repository/[trunk|tags|branches]/projectname I've even hacked the cvs2svn script itself, but to no avail so far. Does anyone have a version that does it the "old" way so we're not mixing up these two policies on svn.zope.org? 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] CMF bug day
On 5 Jul 2005, at 16:15, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Let's do a bug day to clean up outstanding issues before the 1.5.2 release. How about this Thursday, 2004/07/07, from as early to as late as you are up, at irc://irc.freenode.net/#zope-cmf ? Can't be there, friend is in town so after-work-time is booked :( 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 bug day results
On 7 Jul 2005, at 22:06, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 We had a very productive day today: I propose to at least prepare CVS and tag the 1.5.2beta2 release at COB here in the UK. After yesterday's events I decided not to travel this weekend so it might be a good time to do the beta release. Any objections to tagging 1.5.2beta2 at about 5PM british time (noon EST)? 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 bug day results
Folks, CMF 1.5.2beta2 has been tagged in CVS. I will publish the release at some time this weekend. Please hold off on anything but bug fixes for *severe* bugs on the CMF-1_5-branch until CMF 1.5.2 final has been tagged. I would propose a 1 week beta phase and, if everything works out well, CMF 1.5.2 will be virtually unchanged from 1.5.2beta2. 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
[Zope-CMF] CMF 1.5.2beta released
Zope Corporation is pleased to announce the release of version 1.5.2beta2 of the Zope Content Management Framework (CMF). This release is intended for testing purposes only; we do not recommend deploying it to production servers. The final release of version 1.5.2 is expected mid-July 2005. What is the CMF? The Zope Content Management Framework provides a set of services and content objects useful for building highly dynamic, content-oriented portal sites. As packaged, the CMF generates a site much like the Zope.org site. The CMF is intended to be easily customizable, in terms of both the types of content used and the policies and services it provides. Where do I get it? Download it from http://www.zope.org/Products/CMF/CMF-1.5.2beta2 Points of interest include: - "Windows ZIP file", http://www.zope.org/Products/CMF/CMF-1.5.2beta2/ CMF-1.5.2beta2.zip - "Unix tar/gzip archive", http://www.zope.org/Products/CMF/CMF-1.5.2beta2/ CMF-1.5.2beta2.tar.gz . - "Release notes", http://www.zope.org/Products/CMF/CMF-1.5.2beta2/README.txt - "Change history", http://www.zope.org/Products/CMF/CMF-1.5.2beta2/CHANGES.txt - "Installation instructions", http://www.zope.org/Products/CMF/CMF-1.5.2beta2/INSTALL.txt Where do I go to learn more? The CMF mailing list ([EMAIL PROTECTED]) has many participants who are active in supporting the CMF. ...to report bugs? The "CMF Collector":http://www.zope.org/Collectors/CMF is the place to report bugs (please search for existing reports of your issue first!) ___ 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] Moving CMF into SVN
I have created a cvs2svn migration test sandbox for CMF on svn.zope.org: http://svn.zope.org/Sandbox/jens/CMF/ This represents an import from the current state of the CVS repository. It is looking pretty good, except for one niggle: The "branch/tag/trunk"-folders don't represent the direct root for the project files - they all contain a CMF directory which is the root for the project files. I found one cvs2svn FAQ (currently unavailable, server is down) that describes how to create a repository structure as known from svn.zope.org, where the "trunk", "branches" and "tags" directories are *inside* the main project directory. The "normal" way of operation for cvs2svn will create trunk/branches/tags directories at the very top of the repository and "share" them for all projects in the repository. However, that FAQ leads to the outcome described above, which still differs slightly from the other projects on svn.zope.org. Please take a look at the svn sandbox and give me your opinions. It seems that the history is being transferred correctly, just that one small layout problem remains. 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: Moving CMF into SVN
On 11 Jul 2005, at 20:08, Kapil Thangavelu wrote: /note this is a resend original send failed because of attached script which is now inlined. the plone.org and collective cvs->svn migrations basically use cvs2svn on a particular project subdirectory and then move the generated branches/trunk/tags of the svn repo into an svn project subdirectory. i've attached a script i use for migrating sf.net/projects/collective projects to the plone.org collective svn, the generated dumps are transferred by hand and loaded into the existing repository. Thanks Kapil, I'll give that a try. Looks like a "manual" moving of the automatically generated trunk/tags/branches directories is the way to go then. 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] [dev] Site factory - a small proposal
On 14 Jul 2005, at 11:53, yuppie wrote: So I propose a different approach: - move the 'Configured CMF Site' factory to CMFDefault (it is anyway CMFDefault specific because it uses a hardcoded CMFDefault CMFSite) - make 'CMF Site' behave like CMF 1.5's 'Configured CMF Site' If there are no objections, I'll change this on HEAD. Definitely +1 I assume the factory remained in CMFSetup itself to avoid dependencies from CMFDefault to CMFSetup, but I don't think that's a problem - CMFSetup should always be available alongside CMFDefault in a normal setup. 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] [dev] CMFSetup backwards compatibility policy
On 14 Jul 2005, at 17:33, yuppie wrote: I don't think we should try to maintain code compatibility on HEAD. All we should promise is that imports of old profiles work and that we don't break the persistent SetupTool. I suppose right now we're all a little bit in the air about what CVS HEAD is going to become. Will it be CMF 2.0 or CMF 1.6? If we go the more radical way to 2.0 it would be more permissible to have lesss backwards compatibility I'd say... 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
[Zope-CMF] Heads-up: CMF 1.5.2 final Sunday
Hi everyone, I'll take a closer look at the diffs for the changes checked in since 1.5.2beta2 tomorrow, but my gut feeling is that we're OK for the final. I will tag and publish it on Sunday, unless someone has a good reason why I shouldn't. Thanks to all for the fantastic development push we had, especially over the last few weeks. 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: Moving CMF into SVN
Hi all, After trying a few other solutions I have now come up with my own script that organizes the repository the way the rest of svn.zope.org is organized. So we would end up with three CMF-related toplevel projects in SVN: CMF, CMF_Hotfixes and CMF_Extras. These contain subdirectories branches/tags/trunk and the project contents are rooted correctly in trunk or in each of the tags/branches. The script has been tested on local repository copies and it works very well. I would like to go ahead and schedule a migration into the "real" locations at the top of the main svn.zope.org SVN tree, hopefully Sunday because I have time then. Does anyone have problems with Sunday as the day to attempt a "final" migration into SVN? 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
[Zope-CMF] Re: [CMF-checkins] CVS: Products/CMFCore - ActionInformation.py:1.26.2.5
On 16 Jul 2005, at 14:15, Stefan H. Holek wrote: Update of /cvs-repository/Products/CMFCore In directory cvs.zope.org:/tmp/cvs-serv12386/CMFCore Modified Files: Tag: CMF-1_5-branch ActionInformation.py Log Message: CMFCore/ActionInformation.py: Permissions of action categories starting with 'document' are now evaluated in the object context instead of the portal context. This should probably be generalized some more. Could you explain a bit more what problem this is solving? Check-ins into the branch a day before a final production version is released with insufficient problem descriptions that do not seem to be critical bugfixes to CMF scare me. A lot. 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
[Zope-CMF] Re: [CMF-checkins] CVS: Products/CMFCore - ActionInformation.py:1.26.2.5
On 16 Jul 2005, at 15:18, Stefan H. Holek wrote: Don't be scared, I checked in a whole bunch of tests too. ;-) The problem we have is that CMF evaluates permissions for 'object' and 'workflow' actions in the object context, and 'folder' actions in the folder context. Other action categories are evaluated in the context of the portal, which is rarely useful. Plone has 'document' actions and we need permissions checked on the object, not the portal. It is a one line change (with 4 tests). If you really don't want it, we will have to resort to monkey patching ActionInfo. Nah, I'm not going to give you grief about it, it just violates the "nothing but severe bug fixes" policy so soon before the release. This has a limited-enough scope, I just wanted to know what it was for. You'll have more freedom again after I roll the 1.5.2 release tomorrow... 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
[Zope-CMF] CMF 1.5.2 Released
Zope Corporation is pleased to announce the release of version 1.5.2 of the Zope Content Management Framework (CMF). This release marks the latest stable release in the CMF 1.5 series and should be suitable for production use. What is the CMF? The Zope Content Management Framework provides a set of services and content objects useful for building highly dynamic, content-oriented portal sites. As packaged, the CMF generates a site much like the Zope.org site. The CMF is intended to be easily customizable, in terms of both the types of content used and the policies and services it provides. Where do I get it? Download it from http://zope.org/Products/CMF/CMF-1.5.2 Points of interest include: - "Windows ZIP file", http://zope.org/Products/CMF/CMF-1.5.2/CMF-1.5.2.zip - "Unix tar/gzip archive", http://zope.org/Products/CMF/CMF-1.5.2/CMF-1.5.2.tar.gz - "Release notes", http://zope.org/Products/CMF/CMF-1.5.2/README.txt - "Change history", http://zope.org/Products/CMF/CMF-1.5.2/CHANGES.txt - "Installation instructions", http://zope.org/Products/CMF/CMF-1.5.2/INSTALL.txt Where do I go to learn more? The "CMF mailing list":mailto:[EMAIL PROTECTED] has many participants who are active in supporting the CMF. ...to report bugs? The "CMF Collector":http://zope.org/Collectors/CMF is ths place to report bugs (please search for existing reports of your issue first!) --- Jens Vagelpohl[EMAIL PROTECTED] Zetwork GmbHhttp://www.zetwork.com/ ___ 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] [ATTN]: CMF and related packages moved to svn.zope.org
Hi everyone, I just finished migrating the CMF and related projects from cvs.zope.org to svn.zope.org, from CVS to Subversion. All tags and branches have moved, unlike Zope itself there won't be some development using CVS and some using Subversion. These are the packages: - CMF - CMF_Hotfixes - CMF_Extras They packages became new toplevel projects at svn.zope.org, as can be seen here: http://svn.zope.org/ Pending final agreement on the CMF list (or an overriding word from the CMF Pope himself) svn.zope.org will now be the canonical location for CMF sources. They are accessed just like Zope 2.8 and Zope trunk as described here: http://www.zope.org/DevHome/Subversion/ZopeSVNFAQ The only difference is, of course, the last element in the path. Eveerything else works as described in the document linked above. The packages are at... /repos/main/[CMF|CMF_Extras|CMF_Hotfixes] ***To all CMF developers***: Please change your sandboxes and convert them to SVN. If you see any problem please make it known on the CMF list as soon as possible. No data is lost on cvs.zope.org, so if there are show-stoppers we can always switch back to using CVS. Please **do not** commit into cvs.zope.org or svn.zope.org until we have a "yay" or "nay" on which repository we go forward with. ***Next steps***: If we have agreement on using svn.zope.org a couple cleanup tasks need to be done, such as... - "Close off" or "freeze" the CMF projects on cvs.zope.org to either disallow checkins or bring up big fat warnings if someone tries to. Input and ideas on this are welcome, if it was up to me I would use the "commitinfo" file in the CVSROOT to completely prevent updates as the first step. - Change any references to cvs.zope.org in the CMF code to their svn.zope.org equivalents - Change any references to cvs.zope.org on the project web pages, mostly http://www.zope.org/Products/CMF, to point to the svn.zope.org equivalent - Change any download instructions that use CVS to instructions for SVN 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
[Zope-CMF] Re: [ATTN]: CMF and related packages moved to svn.zope.org
On 17 Jul 2005, at 16:33, yuppie wrote: +1 for using the new repository, looks great so far. Two minor issues (almost non-issues): 1.) AFAIK we don't use these keywords: 'Author', 'Date' and 'Revision'. Maybe they should not even be set. 2.) The virtually empty products like CMFCollector, CMFStaging and CMFTracker don't make much sense in a new repository. I guess they should be removed from CMF trunk. (The real products are in CMF_Extras) The keywords are probably set automatically by cvs2svn, there wasn't any operational flag to influence that. You're welcome to clean things up that are obviously not needed. The same is true for the CMFCollector/Tracker/Staging remnants if you find any outside of CMF_Extras. They can be svn removed. You're empowered to wield the axe ;) The migration did not include doing cleanups like that. We will all find little things here and there, and with a heads-up to the group we can clean them up as we see them. 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
[Zope-CMF] Re: [Zope-Coders] [ATTN]: CMF and related packages moved to svn.zope.org
On 17 Jul 2005, at 20:31, Chris Withers wrote: Jens Vagelpohl wrote: - "Close off" or "freeze" the CMF projects on cvs.zope.org to either disallow checkins or bring up big fat warnings if someone tries to. Input and ideas on this are welcome, if it was up to me I would use the "commitinfo" file in the CVSROOT to completely prevent updates as the first step. I like the way this was done with Zope's CVS: the HEAD was cvs delete'ed and files cvs add'ed saying where to go look for the new versions... Right. (Here comes out my CVS ignorance:) Does CVS recursively delete whole projects or does this require some script that deletes folder contents before the folder can be removed? I dimly remember having tried to cvs remove folders at some point and it wouldn't let me. This would have to happen in conjunction with my earlier suggestion about using commitinfo since unlike the Zope repo we really want to completely prevent checkins. 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] [ATTN]: CMF and related packages moved to svn.zope.org
On 18 Jul 2005, at 15:21, Florent Guillaume wrote: I'd like to propose renaming the main branches from things like "CMF-1_5-branch" into just "1.5". I'd be happy about anything that removes the difference between tags and the version number we expose in the software. So if the version number is 1.5.2 it would be nice to have that at a tag "1.5.2". Or "1.5.2beta2" at tag "1.5.2beta2". I would still name branches so that they can be identified as such easier. not sure if the fact that they "reside in /branches" is good enough... 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] [dev] CMFSetup backwards compatibility policy
On 18 Jul 2005, at 12:00, Lennart Regebro wrote: I suppose right now we're all a little bit in the air about what CVS HEAD is going to become. Will it be CMF 2.0 or CMF 1.6? If we go the more radical way to 2.0 it would be more permissible to have lesss backwards compatibility I'd say... I vote for 1.6, at least until it's clear what benefits and roughly what changes 2.0 holds. For all practical purposes the trunk still *is* 1.6, there is nothing radical on it... :) Unless someone gets trigger-happy it would actually be possible to do a 1.6 release series. Since 1.6 would be on its own branch after the first 1.6.0 beta release this does not "block" the trunk for more radical changes for long at all. 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] [dev] CMFSetup backwards compatibility policy
On 18 Jul 2005, at 12:00, Lennart Regebro wrote: I suppose right now we're all a little bit in the air about what CVS HEAD is going to become. Will it be CMF 2.0 or CMF 1.6? If we go the more radical way to 2.0 it would be more permissible to have lesss backwards compatibility I'd say... I vote for 1.6, at least until it's clear what benefits and roughly what changes 2.0 holds. For all practical purposes the trunk still *is* 1.6, there is nothing radical on it... :) Unless someone gets trigger-happy it would actually be possible to do a 1.6 release series. Since 1.6 would be on its own branch after the first 1.6.0 beta release this does not "block" the trunk for more radical changes for long at all. 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] .props, .properties, .metadata
On 20 Jul 2005, at 19:21, Florent Guillaume wrote: The checkin message by Jens says: CMFCore.FSPropertiesObject: Added a deprecation warning to announce the fact that .properties files will disappear in CMF 1.7 and should be replaced with CMFCore.FSMetadata (.metadata) files. (http://svn.zope.org/branches/CMF-1_5-branch/CMFCore/ FSPropertiesObject.py?rev=36843&r1=36461&r2=36843) So am I right in thinking that the warning was added in the wrong place? Yes, you're right. My bad. All fixed now. 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] ToolInit deprecation warnings
On 23 Jul 2005, at 18:21, David Pratt wrote: /usr/local/zope/instance1/Products/CMFCore/utils.py:427: DeprecationWarning: The product_name parameter of ToolInit is deprecated and will be ignored in CMF1.6: kupu DeprecationWarning) I checked with CMFDefault to see it there was a different class to use but it is as follows: from Products.CMFCore.utils import ToolInit ToolInit( 'CMF Default Tool' , tools=tools , icon='tool.gif' ).initialize( context ) What should I be using instead of ToolInit so that code is more futureproof and to avoid the deprecation warnings. Please read the warning more carefully, it spells out very clearly what the problem is. It's not ToolInit that's deprecated, but passing an argument named "product_name" to it. One of your products does. Find it andd eliminate the extra argument. 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: [ATTN]: CMF and related packages moved to svn.zope.org
On 25 Jul 2005, at 14:23, Florent Guillaume wrote: I'm not sure I understand the objection. For a checkout you could do: cd ~tres/svn svn co svn+ssh:///CMF/branches/1.5 CMF-1.5-branch or svn co svn+ssh:///CMF/tags/1.5.2beta2 CMF-1.5.2beta2 There are not hard relations between the name of your checkout and the name in the repository. "1.5" in the repository gives cleaner svn URLs. There hasn't been any answer. Tres, are you still opposed to this cleanup? (A simple svn switch would be all that's needed for the people that already have an existing checkout.) +1 on the renaming from me, FWIW 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: [ATTN]: CMF and related packages moved to svn.zope.org
On 25 Jul 2005, at 15:30, Tres Seaver wrote: There hasn't been any answer. Tres, are you still opposed to this cleanup? (A simple svn switch would be all that's needed for the people that already have an existing checkout.) - -0. I can live with it; I don't want to do the work of converting all the release tags back to the dawn of time, however. From my read this only applies to active branches, which IMHO is only CMF-1_5-branch and, if you're generous (which I am not) the CMF-1_4-branch. Florent: If you want to go ahead and change branches, make sure you send a message to the list explaining what branch names have been changed, and a quick instruction for SVN newbies on how to do the svn switch. 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: Content Type Registry Improvement
On 25 Jul 2005, at 21:06, Tres Seaver wrote: Looks fine. Can you add it with a test? Before that: Move your sandbox to SVN. Don't check into CVS. 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: Content Type Registry Improvement
On 25 Jul 2005, at 22:25, Sidnei da Silva wrote: On Mon, Jul 25, 2005 at 09:26:15PM +0100, Jens Vagelpohl wrote: | | On 25 Jul 2005, at 21:06, Tres Seaver wrote: | >Looks fine. Can you add it with a test? | | Before that: Move your sandbox to SVN. Don't check into CVS. Ok, will do. Is it worth backporting the fix to 1.4? I think that's up to you ;) You know my opinion: For me the 1.4 branch is dead and I won't backport anything to it. If other people want to take responsibility for releases they may freely backport fixes from the active branches. 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] CMF 1.5.3 beta?
On 1 Aug 2005, at 06:04, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Because the Plone guys are trying to release a 2.1RC at OSCOM, and because it would be sensible for them to use the fixes made since 1.5.2 to the 1.5 branch, I'm wondering if we should be tagging a beta of 1.5.3. Any objections? I may or may not get around to making a release for it. I can handle tagging and releasing, matter of fact I *want* to do that to verify my documentation and script changes for release making from SVN and with the new naming conventions. My impression had been that 1.5.2 was the target platform for Plone 2.1, but if they need something that was fixed afterwards I can certainly throw in a quick 1.5.3 beta/release cycle. 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] CMF 1.5.3 beta?
I learned this morning that the Plone 2.1 RC went out (I am told) with CMF 1.5.2. The really crucial fix for them (making the pathwalk in DirectoryView less painfully slow) only really affects people running from SVN checkouts; OTOH, SVN is the only way to get the RC. I assume this means they want to have 1.5.3-final for the pathwalk fix so they can make the Plone 2.1-final release depend on it. Sounds reasonable. Florent: Quick heads-up to me when you're done with your changes, please. If we have a go for the beta I suggest cutting the tag and publishing the release tomorrow morning, about 9am british time. That way zope.org won't have traffic from the Americas, making it marginally more responsive ;) jens P.S.: I too think that more participation from the main "consumers", the Plone developers, is sorely needed on this list. ___ 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] Plone participation in the CMF list
We have contributed quite a few bug fixes to CMF, though that has been hampered by problems getting CVS access (I sent in my contributor form over a year ago and have yet to hear anything; as Tres has indicated, this has been a problem for several other Plone developers as well). I'm hoping that will move along faster now. That's out of the hands of any of the active developers unfortunately. We have also offered some fairly substantial pieces of code to the CMF (Archetypes, CMFFormController, SpeedPack), but have met with indifference and/or active rejection. I have several products I think could find a home in the CMF, but given the response to previous offers, I'm not sure it's worth the trouble to make the offer. I don't claim to know the details of how that went down, but I distinctly remember from the time both Tres and I were still at ZC that Tres offered to incorporate AT and have it become part of CMF. I'm not sure who exactly he talked to, but from what I remember that was met with the same indifference you're attesting the CMF community. In general, I sense a fair amount of hostility to Plone expressed on the list in the form of gratuitous sniping. If you want us to participate, it might help to play more nicely. I would like to note that CMF != Plone. Plone is the largest "consumer", correct, but that doesn't mean everyone who uses CMF uses Plone, or that individual participants are forbidden to have a negative opinion about Plone. Life on mailing lists is tough and full of taunts and flame throwing. The CMF list is actually one of the least "offensive" lists I am on. That said, I have heard some good ideas from e.g. Paul about how to re-align the "factions" better in the future and I hope both Paul and Tres can talk about it more in Vienna, and pull in suitable Plone leaders. It would help everyone if the CMF side opened up a little more to ideas coming down from Plone, and if the Plone side stopped reinventing wheels that would be much better off (and benefit everyone) in the CMF or other non-Plone core products. 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: Plone participation in the CMF list
On 1 Aug 2005, at 17:53, Geoff Davis wrote: On Mon, 01 Aug 2005 17:30:20 +0100, Jens Vagelpohl wrote: It would help everyone if the CMF side opened up a little more to ideas coming down from Plone, and if the Plone side stopped reinventing wheels that would be much better off (and benefit everyone) in the CMF or other non-Plone core products. Perhaps some specifics would help. * What wheels do you think Plone has reinvented? * Are there any particular things in Plone that you think should be pushed down into CMF? I don't have anything specific in front of me right now. It is a comment on the massive development effort going into Plone but the trickle that happens at the CMF level, and that most of the CMF level stuff is done by non-Plone people. The general mindset of most Plone developers, as I perceive it from the CMF side, seems to be one of "I'm in Plone code, and I know what to do here, and I don't need to look beyond my world". Very few developers have a broader view and even think of pushing generic functionality or even specific improvements to core functionality that originates in the CMF down to the CMF level. It seems easier for them to monkeypatch and override directly inside Plone code. 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] CMF 1.5.3 beta?
If we have a go for the beta I suggest cutting the tag and publishing the release tomorrow morning, about 9am british time. That way zope.org won't have traffic from the Americas, making it marginally more responsive ;) Great, thanks! I am planning to release Plone 2.1 final in 2 weeks. Would be convenient to have CMF 1.5.3 final by then. Yes, if we can keep the beta cycle short and the changeset manageable. With everyone helping out testing the changed bits that came in since 1.5.2 and no big isssues arising a single beta can be sufficient. I'm here, I'm here . If you'd dis Plone a little less I am sure more of us would chime in more often ;-) Don't tell me you're scared of certain peoples' personal opinion... :P 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] CMF 1.5.3 beta?
Alright, it's out now. I probably spent 90% of the last two hours fighting zope.org which was near-unresponsive... Anyway, since this is a beta the usual precautions apply: - No non-critical-bugfix checkins on the CMF 1.5 branch until CMF 1.5.3 final is out - Please help test the release, especially the changes shown below that have flown in since the last release. CMF 1.5.3 will be the release Plone 2.1 final is based on (if nothing bad happens in the meantime), it will see very widespread use, so good quality control is important. I am hoping we can have a quick beta cycle with just this beta release. Please test! ;) --- Bugs Fixed - Changed the INSTALL_SVN instructions to conform to the new branch and tag naming scheme instituted for the subversion repository. - Apply an interim fix for slow pathwalking implementation in development mode on Windows (http://www.zope.org/Collectors/ CMF/367) Note that a better fix would be to leverage pywin32 APIs for file / directory monitoring. - FSObject.manage_doCustomize() was broken for folderish objects on Zope 2.8 because manage_permission requires a context to work. (see http://www.zope.org/Collectors/CMF/368) - CMFCore/FSPropertiesObject and CMFCore/FSMetadata: Removed a wrongly inserted DeprecationWarning in the FSPropertiesObject class and put it into the FSMetadata class. We are not deprecating ".props" files, but ".properties" and ".security". - Change CVS checkout documentation to their equivalent Subversion instructions - In CMFSetup, make sure to give special treatment to both CVS and .svn folders where this is necessary (e.g. to implicitly skip them when importing profiles) - Made sure FSDVTest always deletes its temporary folder on tearDown. (http://www.zope.org/Collectors/CMF/106) - Fix DefaultWorkflowDefinition bug on isActionSupported() for the keywargs support to reflect DCWorkflowDefinition changes. Add a test case for this definition as well. Others - CMFCatalogAware: reindexObjectSecurity() now always reindexes the catalog objects without changing their catalog uid. This is useful for third-party code that indexes objects with special uids. - 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
[Zope-CMF] CMF 1.5.3-beta released
The CMF developer community and Zope Corporation are pleased to announce the release of version 1.5.3-beta of the Zope Content Management Framework (CMF). This release is intended for testing purposes only; we do not recommend deploying it to production servers. The final release of version 1.5.3 is expected to land within about 10 days. What is the CMF? The Zope Content Management Framework provides a set of services and content objects useful for building highly dynamic, content-oriented portal sites. As packaged, the CMF generates a site much like the Zope.org site. The CMF is intended to be easily customizable, in terms of both the types of content used and the policies and services it provides. Where do I get it? Download it from http://zope.org/Products/CMF/CMF-1.5.3-beta Points of interest include: - "Windows ZIP file", http://zope.org/Products/CMF/CMF-1.5.3-beta/CMF-1.5.3-beta.zip - "Unix tar/gzip archive", http://zope.org/Products/CMF/CMF-1.5.3-beta/CMF-1.5.3- beta.tar.gz . - "Release notes", http://zope.org/Products/CMF/CMF-1.5.3-beta/README.txt - "Change history", http://zope.org/Products/CMF/CMF-1.5.3-beta/CHANGES.txt - "Installation instructions", http://zope.org/Products/CMF/CMF-1.5.3-beta/INSTALL.txt Where do I go to learn more? The CMF mailing list ([EMAIL PROTECTED]) has many participants who are active in supporting the CMF. ...to report bugs? The "CMF Collector":http://zope.org/Collectors/CMF is the place to report bugs (please search for existing reports of your issue first!) - Jens Vagelpohl [EMAIL PROTECTED] ___ 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: xsl/xul and FSPageTemplate
On 2 Aug 2005, at 11:11, Duncan Booth wrote: Julien Anguenot wrote: Why don't you create your own FSXSLTemplate object ? It's pretty easy to register this kind of objects within the CMF using the dedicated registry. It might even sub-class FSPageTemplate if it makes sense in your case. I would do it like this myself. We could, but kupu seems like the wrong place to be registering such as general purpose object. A better place might be Archetypes (both kupu and archetypes currently register xsl file extensions), but it sounds to me like a general enough requirement that possibly it should just be in CMFCore (also, kupu can run without Archetypes being present & vice versa, so if either defined a suitable class they would both need to define it). CMFCore is probably a good-enough place. If you want to provide code I'll shepherd it into Subversion, into the trunk and, after the 1.5.3 final is released, the 1.5 branch. Don't forget to add the necessary unit tests etc. 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: Plone participation in the CMF list
On 2 Aug 2005, at 13:27, Florent Guillaume wrote: Tres Seaver <[EMAIL PROTECTED]> wrote: I think the discussion around Archetypes, in particular, ended up stalled over the question of whether to "code generation" design should be preferred over "configuration-based" design (as found in CPSSchemas, for instance). Also now that Zope 3 is taking more and more importance in CMF, any schema-based solution should be based on Zope 3 schemas. IMO both Archetypes and CPSSchemas are too big frameworks to include in CMF. Absolutely. I think at least at the CMF developer level we're in agreement that the direction is "towards Zope 3 via Five". Any decision we make about including new code must be made with that in mind. Which leaves the question, because I simply don't know: What is the direction Plone is moving in? 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: xsl/xul and FSPageTemplate
On 4 Aug 2005, at 00:45, Andy McKay wrote: Not sure if you've written this, but a general FSXMLTemplate (not just XSL) would be nice for the rendering of xml Page Templates. In particular the problem I've wrangled with is inserting dynamically the Where that really needs to be: tal:attributes="href string:$portal_url/rss.xsl"?> Speaking of that, for one of my sites where I want to have XHTML 1.0 strict, I have tried to make the output compliant so it renders as the "correct" type, "application/xhtml+xml" I believe it was, in the browsers that understand it. This was more of a game than anything else because that garbage browwser, IE, has no idea what to do with that. I have found it impossible to get rendered output that is truly compliant because the FSPageTemplate rendering would always insert an empty line before what is supposed to be the very first element, the "main metal macro because then the parser would barf and claim the template is erroneous. So IMHO there are more problems than "just" retaining a file extension. 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
[Zope-CMF] CMF 1.5.3 tomorrow
I plan to package up CMF 1.5.3 final tomorrow so it's ready for the Plone 2.1 release next week. SVN shows no changes since the beta, except for one small formatting change in CHANGES.txt. One additional bug came in via the collector and it seems an easy fix so I'll look at it later today. 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] CMF 1.5.3 released
On 7 Aug 2005, at 09:59, Jens Vagelpohl wrote: The CMF developer community and Zope Corporation are pleased to announce the release of version 1.5.3 of the Zope Content Management Framework (CMF). This release marks the latest stable release in the CMF 1.5 series and should be suitable for production use. ...and the 1.5 branch is open for development again. This must have been the shortest and most trouble-free beta phase for any CMF release. I hope that doesn't mean no one tested the beta ;) 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
[Zope-CMF] CMF 1.5.3 released
The CMF developer community and Zope Corporation are pleased to announce the release of version 1.5.3 of the Zope Content Management Framework (CMF). This release marks the latest stable release in the CMF 1.5 series and should be suitable for production use. What is the CMF? The Zope Content Management Framework provides a set of services and content objects useful for building highly dynamic, content-oriented portal sites. As packaged, the CMF generates a site much like the Zope.org site. The CMF is intended to be easily customizable, in terms of both the types of content used and the policies and services it provides. Where do I get it? Download it from http://zope.org/Products/CMF/CMF-1.5.3 Points of interest include: - "Windows ZIP file", http://zope.org/Products/CMF/CMF-1.5.3/CMF-1.5.3.zip - "Unix tar/gzip archive", http://zope.org/Products/CMF/CMF-1.5.3/CMF-1.5.3.tar.gz - "Release notes", http://zope.org/Products/CMF/CMF-1.5.3/README.txt - "Change history", http://zope.org/Products/CMF/CMF-1.5.3/CHANGES.txt - "Installation instructions", http://zope.org/Products/CMF/CMF-1.5.3/INSTALL.txt Where do I go to learn more? The "CMF mailing list":mailto:[EMAIL PROTECTED] has many participants who are active in supporting the CMF. ...to report bugs? The "CMF Collector":http://zope.org/Collectors/CMF is ths place to report bugs (please search for existing reports of your issue first!) - Jens Vagelpohl [EMAIL PROTECTED] ___ 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] [dev] i18n improvements - a proposal
I'd like to work at least on the first 3 items for CMF 1.6. AFAICS this should not break anything on Zope 2.8.0. But maybe we should anyway make Zope 2.8.1 the required platform for CMF 1.6. Making Zope 2.8.1 the required platform for CMF 1.6 is fine IMHO, I believe we have plenty of freedom right now. Any time estimate for those first tasks? A big +1 from me for anything that allows us to do internationalization with stuff we already have available and without add-on products. 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: [dev] i18n improvements - a proposal
Does that mean you are voting against using 'cmf_calendar' in CMFCalendar? The reason why I'd like to use a different domain for CMFCalendar is that CMFCalendar is our example add-on product. This way we *use* different domains for Actions and TypeInfos within the CMF, showing how to do that and making sure it works. Is it our example add-on product? It's not been all that well- maintained to be deserving of that status... ~8-0 My 2¢ are that I'm all for making sure different domains work well, and CMFCalendar *seems* the only suitable add-on in the software package. It's probably a good idea to just use that, and then maybe a single domain for everything else in the base package as Florent suggests. 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
[Zope-CMF] Re: [CMF-checkins] SVN: CMF/trunk/CMFDefault/profiles/default/types/CMF_BTree_Folder.xml please don't forget to set svn:eol-style native
On 11 Aug 2005, at 12:05, Yvo Schubbe wrote: Log message for revision 37859: please don't forget to set svn:eol-style native Changed: _U CMF/trunk/CMFDefault/profiles/default/types/CMF_BTree_Folder.xml -=- Property changes on: CMF/trunk/CMFDefault/profiles/default/types/ CMF_BTree_Folder.xml ___ Name: svn:eol-style + native Sorry, my bad. Do we have some developer doc hanging around somewhere where we can collect those "must do" tasks? Maybe there should be one that is part of the package documentation, some small "dos and don'ts for CMF developers"? 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-checkins] SVN: CMF/trunk/CMFDefault/profiles/default/types/CMF_BTree_Folder.xml please don't forget to set svn:eol-style native
On 11 Aug 2005, at 12:10, Raphael Ritz wrote: Sorry, my bad. Do we have some developer doc hanging around somewhere where we can collect those "must do" tasks? How about http://www.zope.org/DevHome/Subversion/ZopeSVNFAQ (note the third point there) Excellent. It's set up that way in my subversion config now. 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
[Zope-CMF] Tope Date Criteria fix
I have put changes that fix the arguably completely broken behavior for CMFTopic Date criteria on a branch: http://svn.zope.org/CMF/branches/jens-collector-339-branch/ For those who are interested, it would be nice if you could give it a quick test and see if there are "logic errors". The only drawback is the fact that there really isn't much we can do to be 100% backwards compatible as far as the old behavior goes for people who might rely on it. What is the backwards-compatibility consensus as far as changes go that will not break old software, but fix a really broken behavior? 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
[Zope-CMF] CMF 1.5.4 for Plone 2.1 final
Stefan Holek has asked be if we could do another "quickie release" and I promised we would, given we have at least one beta. He wants the fix for this issue in the final: http://www.zope.org/Collectors/CMF/372 To that effect, I want to do a beta Saturday afternoon or Sunday morning and a final release at the end of next week. Anyone have any problems with this plan? 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
[Zope-CMF] Re: CMF 1.5.4 for Plone 2.1 final
Stefan Holek has asked be if we could do another "quickie release" and I promised we would, given we have at least one beta. He wants the fix for this issue in the final: http://www.zope.org/Collectors/CMF/372 If nobody in the community thinks they are at risk here (i.e., they are running old Apache with the bug for which forcing a Content-Length header was the workaround), then I am OK with this fix. This "fix" has nothing to do with the ZServer issue - all we do in CMF is prevent setting content-length in the CMF code, ZServer will still add the zero-length header. This mirrors the behavior OFS.Image has now and is therefore 100% safe. The ZServer issue itself will be dealt with on a different time line. To that effect, I want to do a beta Saturday afternoon or Sunday morning and a final release at the end of next week. Anyone have any problems with this plan? CMF 1.5.2 and 1.5.3 were both created FBO the Plone 2.1 release cycle; I don't like the rhythm here, and would rather be making betas / RCs for the Plone RCs. Therefore, this will be the last time that we create third-dot releases in advance of the Plone final release. I agree. This is a matter of concerted planning instead of the current "we think we have something to release, please make a CMF release for us". 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
[Zope-CMF] CMF 1.5.4-beta released
The CMF developer community and Zope Corporation are pleased to announce the release of version 1.5.4-beta of the Zope Content Management Framework (CMF). This release is intended for testing purposes only; we do not recommend deploying it to production servers. The final release of version 1.5.4 is expected to land within the next 10 days. What is the CMF? The Zope Content Management Framework provides a set of services and content objects useful for building highly dynamic, content-oriented portal sites. As packaged, the CMF generates a site much like the Zope.org site. The CMF is intended to be easily customizable, in terms of both the types of content used and the policies and services it provides. Where do I get it? Download it from http://zope.org/Products/CMF/CMF-1.5.4-beta Points of interest include: - "Windows ZIP file", http://zope.org/Products/CMF/CMF-1.5.4-beta/CMF-1.5.4-beta.zip - "Unix tar/gzip archive", http://zope.org/Products/CMF/CMF-1.5.4-beta/CMF-1.5.4- beta.tar.gz . - "Release notes", http://zope.org/Products/CMF/CMF-1.5.4-beta/README.txt - "Change history", http://zope.org/Products/CMF/CMF-1.5.4-beta/CHANGES.txt - "Installation instructions", http://zope.org/Products/CMF/CMF-1.5.4-beta/INSTALL.txt Where do I go to learn more? The CMF mailing list ([EMAIL PROTECTED]) has many participants who are active in supporting the CMF. ...to report bugs? The "CMF Collector":http://zope.org/Collectors/CMF is the place to report bugs (please search for existing reports of your issue first!) - Jens Vagelpohl [EMAIL PROTECTED] ___ 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] CMF 1.5.4-beta
So hopefully this is the last pre-Plone 2.1 release. As always, please test this is as good as you can and don't check anything that's not an urgent bug fix into the 1.5 branch until 1.5.4 final is out, which I plan on doing this coming weekend unless something bad happens. The changes, meaning the items people should look at closely over the next week, were the following: --- Bug Fixes - CMFCore.utils: The return value from _mergedLocalRoles allowed direct manipulation of objects' local role settings since it contained references to the actual values instead of copies. (http://www.zope.org/Collectors/CMF/376) - CMFTopic.DateCriteria: The behavior and naming of date criteria operators was very confusing and in many cases unexpected and wrong. For that reason e.g. Plone replaced the implementation with a more user-friendly handling which is hereby introduced to CMF proper. (http://www.zope.org/Collectors/CMF/339) - CMFCore.PortalContent, CMFCore.FSSTXMethod, CMFTopic.Topic, CMFDefault.SkinnedFolder: Cache headers from the Caching Policy Manager never got set for DTML-based skins due to the way the view template __call__ method was invoked. (http://www.zope.org/Collectors/ CMF/374) - CMFCore.FSImage and FSFile: Unlike the current behavior of Zope itself, FSImage and FSFile would set a content-length response header for 304 (not modified) responses, which should not be done according to RFC 2616. It won't do so anymore, but Zope itself will still force a content-length header in ZServer.HTTPResponse. This misbehavior has been filed as a Zope issue (http://www.zope.org/Collectors/ Zope/1866). (http://www.zope.org/Collectors/CMF/372) - PortalFolder: Improved the _checkId method. Method Aliases mask objects with matching IDs. Thus _checkId() and checkIdAvailable() now make sure non-managers can't create objects with IDs already taken by Method Aliases of the current folder. - CMFDefault.Image and CMFDefault.File: When calling the constructor, any intelligent content type detection would be destroyed by the call to initialize Dublin Core values, which would overwrite the content_type. It is now preserved, if possible. (http://www.zope.org/Collectors/CMF/370) Features - CMFTopic.Topic: Made Topics a tad more useful by subclassing from CMFDefault.SkinnedFolder instead of CMFCore.PortalFolder, because SkinnedFolder is CatalogAware. Topics now offer useful information for Title, Description and SearchableText, so Topic objects can be located in the portal by using the standars search facilities. (http://www.zope.org/Collectors/CMF/53) Others - CMFCore.PortalFolder._checkId() allows root doted prefixed name object overrides. --- 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] RFC: Flon functionality ported to CMF?
On 27 Aug 2005, at 02:30, Rob Miller wrote: sidnei has written an excellent product called Flon (i.e. Five for Plone) which provides a user interface for examining the Z3 interfaces that an object may have, and for assigning marker interfaces to particular content instances. whit morriss has written a PLIP (http://plone.org/products/plone/roadmap/104) which proposes integrating this into the Plone core. this seems to me to be the sort of thing that really should live in CMF itself. I have to claim ignorance, unfortunately, as far as the technical details go since I haven't done anything with Five or Z3 myself. But since we are moving more and more towards tighter Five integration it seems that any software designed with the same goal is a good candidate for the CMF. 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] A funding initiative to improve the software stack
On 25 Aug 2005, at 18:27, Paul Everitt wrote: Hi, CMF folks. Munwar and I would like to start public discussion about Goldegg, a funding initiative for advancing Zope 3 in the Plone/CMF/Five software stack. In summary, Goldegg provides funding to get Zope 3 into the near-term roadmaps of the stack. Specifically, the funding initiative helps get the leaders of these roadmaps working in coordination on the next releases. Hm. I think we're waiting for more details ;) But in general, kudos to the scheme as a whole. It is a fantastic idea to put actual customer funding into the freely available software stack which hasn't seen much of that in its history. Most funding has always gone to specific customer projects where good ideas or software tend to be locked up, out of reach of the core software package. 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: RFC: Flon functionality ported to CMF?
On 29 Aug 2005, at 01:37, whit wrote: Implementing this tool as a utility and making it backwardly compatible (ie available from getToolByName) might be useful for everyone, and not further pollute the portal root with damn tool objects. Yes, there certainly is a terrible tool proliferation, probably more painfully in Plone than in the CMF. IMHO it wouldn't be so bad if those were optional components that provide optional functionality, but most of them must be there or the site breaks. 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: CMFSetup
On 1 Sep 2005, at 14:18, Florent Guillaume wrote: Please followup here about your progress, we (Nuxeo) should be working on CMFSetup a lot this month too. It might be useful for all those items that are not connected to a collector issue (where you can "accept" it and signal that you are working on it) to introduce some formalized way of announcing "Hey, I'm working on/have plans to work on X." to prevent collisions. One very simple way to achieve it would be to create a collector entry for it and assign it to oneself immediately. 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
