Tres Seaver wrote:
snip
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
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
-
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:
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:
-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
-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
