[Zope-CMF] Re: Modifications using GS profiles
Hi Tres! Tres Seaver wrote: yuppie wrote: Tres Seaver wrote: yuppie wrote: Tres Seaver wrote: If we had the upgrade machinery in place, we could scrap non-purging mode altogether -- its purpose is to allow for "controlled" application of changes to existing configuration without full replacement. [...] Well. If we don't use the non-purging mode we can't write changes as profile snippets. Should upgrade steps always be implemented in pure Python without using any XML files? I would say that the "execute-while-parse" model of our current profile import driver is wrong for upgrades, but it would be possible. The upgrade step could do the checking that a given "upgrade-only" extension should be imported, and then import it (perhaps passing 'no_purge' as a flag). Meanwhile, we would disable / remove any UI for setting that flag outside an upgrade. I removed the UI for setting that flag long ago. But extension profiles are always applied in non-purging mode, so the upgrade machinery doesn't help us to get rid of that mode. I also would like to get rid of it, but that is only possible if we have a delta profile machinery that supersedes extension profiles. The CMF 2.1 branch is not as stable as it should be. Adding the 'upgrade steps' feature might be low risk, but the other changes on the sprint branch look more risky to me. I'm a bit afraid merging them will destabilize the 2.1 branch further. I don't think so. The other changes split out the UI for setting the baseline profile (ordinarily done only at site creation) and showing available extensions. I think the cleanup there is highly unlikely to cause instability: the only change is that we no longer require (or even allow) people to set extension profiles as "faux" baselines in order to import them. If you say so, I withdraw my objections. Cheers, Yuppie ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] Re: Modifications using GS profiles
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 yuppie wrote: > Hi Tres! > > > Tres Seaver wrote: >> yuppie wrote: >> >>> But that code doesn't improve the non-purging mode. The changes Wichert >>> proposed make sense with or without the 'upgrade steps' feature. >> If we had the upgrade machinery in place, we could scrap non-purging >> mode altogether -- its purpose is to allow for "controlled" application >> of changes to existing configuration without full replacement. >> Wichert's rationale was specifically: >> >>> The particular reason I'm interested in this is that for Plone we are >>> playing with using GenricSetup profiles as part of the migration code. >>> This means we can write a lot less python code but just write changes >>> as profile snippets. > > Well. If we don't use the non-purging mode we can't write changes as > profile snippets. Should upgrade steps always be implemented in pure > Python without using any XML files? I would say that the "execute-while-parse" model of our current profile import driver is wrong for upgrades, but it would be possible. The upgrade step could do the checking that a given "upgrade-only" extension should be imported, and then import it (perhaps passing 'no_purge' as a flag). Meanwhile, we would disable / remove any UI for setting that flag outside an upgrade. > BTW: Are there any unit tests for the upgrade steps feature? I'll defer to Rob: he was porting the code from the CPS add-on. >>> CMF 2.1 beta has some serious site manager issues. Please let's focus on >>> resolving these issues first. >> I'm really just lobbying to have the GS work tested and merged. Fixing >> ths LSM stuff is in the hands of a different set of folks, I think. >> Rob, how did stuff go at Sorrento? > > The CMF 2.1 branch is not as stable as it should be. Adding the 'upgrade > steps' feature might be low risk, but the other changes on the sprint > branch look more risky to me. I'm a bit afraid merging them will > destabilize the 2.1 branch further. I don't think so. The other changes split out the UI for setting the baseline profile (ordinarily done only at site creation) and showing available extensions. I think the cleanup there is highly unlikely to cause instability: the only change is that we no longer require (or even allow) people to set extension profiles as "faux" baselines in order to import them. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGHApu+gerLs4ltQ4RAlqXAKCHYfNjz+2c3iYn7GaZ/kwgimYNUwCggMDM bb7izET8Lqq8MAHqARUdFTE= =MmTO -END PGP SIGNATURE- ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] [dev] unresolved site manager related issues
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10 Apr 2007, at 10:30, yuppie wrote: Currently non-five.lsm site managers don't work in CMF, see this thread: http://mail.zope.org/pipermail/zope-cmf/2007-March/025817.html Proposed solutions: a) reverting most 'tools as utilities' changes (Kapil) http://mail.zope.org/pipermail/zope-cmf/2007-March/025817.html b) supplementing five.lsm (Hanno) http://mail.zope.org/pipermail/zope-cmf/2007-March/025822.html c) improving five.lsm (Rocky) AFAICS this is an other attempt to resolve the same issue: http://mail.zope.org/pipermail/zope-cmf/2007-March/025708.html We have to decide which way to go. I prefer c) if it works, b) otherwise. Same here. c) first, then b). Strongly against a). jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFGG4yHRAx5nvEhZLIRAmsxAKCjxMx7xU5gG46LRvxhwOaA77S4NACgoBU/ Y9gWyWCp06aJE7L+J6gW5WM= =2doS -END PGP SIGNATURE- ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] CMF Tests: 9 OK, 2 Unknown
Summary of messages to the cmf-tests list. Period Mon Apr 9 12:00:00 2007 UTC to Tue Apr 10 12:00:00 2007 UTC. There were 11 messages: 11 from CMF Unit Tests. Unknown --- Subject: UNKNOWN : CMF-2.1 Zope-trunk Python-2.4.4 : Linux From: CMF Unit Tests Date: Mon Apr 9 21:34:52 EDT 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-April/004616.html Subject: UNKNOWN : CMF-trunk Zope-trunk Python-2.4.4 : Linux From: CMF Unit Tests Date: Mon Apr 9 21:37:52 EDT 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-April/004618.html Tests passed OK --- Subject: OK : CMF-1.5 Zope-2.7 Python-2.3.6 : Linux From: CMF Unit Tests Date: Mon Apr 9 21:22:51 EDT 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-April/004608.html Subject: OK : CMF-1.5 Zope-2.8 Python-2.3.6 : Linux From: CMF Unit Tests Date: Mon Apr 9 21:24:21 EDT 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-April/004609.html Subject: OK : CMF-1.5 Zope-2.9 Python-2.4.4 : Linux From: CMF Unit Tests Date: Mon Apr 9 21:25:52 EDT 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-April/004610.html Subject: OK : CMF-1.6 Zope-2.8 Python-2.3.6 : Linux From: CMF Unit Tests Date: Mon Apr 9 21:27:22 EDT 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-April/004611.html Subject: OK : CMF-1.6 Zope-2.9 Python-2.4.4 : Linux From: CMF Unit Tests Date: Mon Apr 9 21:28:52 EDT 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-April/004612.html Subject: OK : CMF-2.0 Zope-2.9 Python-2.4.4 : Linux From: CMF Unit Tests Date: Mon Apr 9 21:30:22 EDT 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-April/004613.html Subject: OK : CMF-2.0 Zope-2.10 Python-2.4.4 : Linux From: CMF Unit Tests Date: Mon Apr 9 21:31:52 EDT 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-April/004614.html Subject: OK : CMF-2.1 Zope-2.10 Python-2.4.4 : Linux From: CMF Unit Tests Date: Mon Apr 9 21:33:22 EDT 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-April/004615.html Subject: OK : CMF-trunk Zope-2.10 Python-2.4.4 : Linux From: CMF Unit Tests Date: Mon Apr 9 21:36:22 EDT 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-April/004617.html ___ 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: GenericSetup: catalog.xml ideas
yuppie, on 2007-04-09:
> Looks fine, I checked it in:
> http://svn.zope.org/?rev=74050&view=rev
> http://svn.zope.org/?rev=74051&view=rev
Merci.
>> BTW, I am slightly freaked out by the following. In that test file
>> there is this test:
>>
>> self.assertEqual(adapted.body, _CATALOG_BODY % ('', _ZCTEXT_XML))
>>
>> The test passes of course. But when I copy that line so the test is
>> run twice, like this:
>>
>> self.assertEqual(adapted.body, _CATALOG_BODY % ('', _ZCTEXT_XML))
>> self.assertEqual(adapted.body, _CATALOG_BODY % ('', _ZCTEXT_XML))
>>
>> then the second test throws an error!
>>
>> [...]
>>
>> Going in with the pdb also throws that error when you try to print
>> adapted.body twice.
>>
>> I will loan you my "Here be dragons" sign. ;-)
>
> Fixed as well.
Ah, thanks. Tested and found working now. That keeps me sane. :)
--
Maurits van Rees | http://maurits.vanrees.org/ [NL]
Work | http://zestsoftware.nl/
"Do not worry about your difficulties in computers,
I can assure you mine are still greater."
___
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] [dev] unresolved site manager related issues
Hi! This is an attempt to summarize the unresolved issues. Please correct me if something is wrong or incomplete. 1.) sub-sites (KSS issue): -- Currently non-five.lsm site managers don't work in CMF, see this thread: http://mail.zope.org/pipermail/zope-cmf/2007-March/025817.html Proposed solutions: a) reverting most 'tools as utilities' changes (Kapil) http://mail.zope.org/pipermail/zope-cmf/2007-March/025817.html b) supplementing five.lsm (Hanno) http://mail.zope.org/pipermail/zope-cmf/2007-March/025822.html c) improving five.lsm (Rocky) AFAICS this is an other attempt to resolve the same issue: http://mail.zope.org/pipermail/zope-cmf/2007-March/025708.html We have to decide which way to go. I prefer c) if it works, b) otherwise. 2.) GenericSetup components handler: http://mail.zope.org/pipermail/zope-cmf/2007-March/025743.html http://www.zope.org/Collectors/CMF/473 Hanno volunteered to work on this, but the fix depends on resolving issue 1. 3.) missing five.lsm UI: IIRC Rocky planed to add a basic UI for managing components. In my sandbox I have a view for editing the XML representation (as used in GenericSetup), but that depends on resolving issue 2. Cheers, Yuppie ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] CMF Collector: Open Issues
The following supporters have open issues assigned to them in this collector (http://www.zope.org/Collectors/CMF). Assigned and Open dreamcatcher - "setChainForPortalTypes doesn't allow to set default chain", [Accepted] http://www.zope.org/Collectors/CMF/475 mhammond - "Windows DevelopmentMode penalty in CMFCore.DirectoryView", [Accepted] http://www.zope.org/Collectors/CMF/366 Pending / Deferred Issues - "FSPropertiesObject.py cannot handle multiline input for lines, text attributes", [Deferred] http://www.zope.org/Collectors/CMF/271 - "Can't invalidate skin items in a RAMCacheManager", [Pending] http://www.zope.org/Collectors/CMF/343 - "workflow notify success should be after reindex", [Deferred] http://www.zope.org/Collectors/CMF/389 - "Possible bug when using a BTreeFolder Member folder", [Pending] http://www.zope.org/Collectors/CMF/441 - "purge_old in runAllImportSteps not working", [Pending] http://www.zope.org/Collectors/CMF/455 - "Danger from Caching Policy Manager", [Pending] http://www.zope.org/Collectors/CMF/460 - "properties setup handler: support for non-ascii strings", [Pending] http://www.zope.org/Collectors/CMF/468 - "GenericSetup does not handle non-ascii data well", [Pending] http://www.zope.org/Collectors/CMF/471 - "autocreation of catalog indexes", [Pending] http://www.zope.org/Collectors/CMF/472 - "[GS] Error when choosing initial_configuration ", [Pending] http://www.zope.org/Collectors/CMF/473 Pending / Deferred Features - "Favorite.py: queries and anchors in remote_url", [Pending] http://www.zope.org/Collectors/CMF/26 - "DefaultDublinCore should have Creator property", [Pending] http://www.zope.org/Collectors/CMF/61 - "Document.py: universal newlines", [Pending] http://www.zope.org/Collectors/CMF/174 - "portal_type is undefined in initialization code", [Pending] http://www.zope.org/Collectors/CMF/248 - "CMFTopic Does Not Cache", [Deferred] http://www.zope.org/Collectors/CMF/295 - "Wishlist: a flag that tags the selected action.", [Pending] http://www.zope.org/Collectors/CMF/301 - "CMFDefault should make use of allowCreate()", [Pending] http://www.zope.org/Collectors/CMF/340 - "Nested Skins", [Deferred] http://www.zope.org/Collectors/CMF/377 - "CatalogVariableProvider code + tests", [Pending] http://www.zope.org/Collectors/CMF/378 - "CMF needs View-based TypeInformation", [Pending] http://www.zope.org/Collectors/CMF/437 - "New getNextEvent Method", [Pending] http://www.zope.org/Collectors/CMF/462 ___ 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] LSM stuff
Tres Seaver wrote: Fixing this LSM stuff is in the hands of a different set of folks, I think. Rob, how did stuff go at Sorrento? > > > Tres. I am just back from holidays that followed the Sorrento sprint. Reading the list did not allow me to understand if we came to a consensus regarding the getToolByName/getUtility question. Tres seems to imply there is one. Can someone make a summary/statement of the current state of thoughts ? Thanks -- Godefroid Chapelle (aka __gotcha)- BubbleNet http://bubblenet.be ___ 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
