[Zope-CMF] Re: CMF 1.5 beta coming -- last call before feature freeze!

[Tres Seaver]

BTW, I am seeing a ton of delayed / failed mail delivery to your 
mail.udag.de address.  Maybe you'll see this on gmane.org, or something.

yuppie wrote:

> Hi!
> 
> 
> These issues are still unresolved:
> 
> a.) mark getActionById() as deprecated / add a warning
> 
>     -> ok?

+1

> b.) CMFSetup
> 
>>>   #1:     Should be able to steal UI from the "Configured CMF Site" bit
>>>           (I added the underlying machinery in order to support that).
>>>
>>>   #2:
> 
> 
>     remove 'Compare Snapshots' button from 'Snapshots' tab
> 
>     -> ok?

+1.

>>>   #5:
> 
> 
>     fix import of workflow bindings

I saw some checkins from you yesterday on the workflow export / import. 
  What is left?

>>>   #6:     The page templates we are using need to be CR-free.  We may
>>>           need to change the mechanism we use for building the Windows
>>>           release binary, such that it checks the sources out and
>>>           zips them on a Windows system (I can't do that easily myself).
>>>   #7:     I can't fix it, as I don't run Windows.
> 
> 
> #8:    'Configured CMF Site' factory is still experimental
> 
>     -> remove registration on release branch?

Or add a note on the factory form which explains that the site will need 
further tweaking.

> #9:    some unittests fail if run with test.py

This is how I run them:

   $ bin/zopectl run /path/to/all_cmf_tests.py
   ... # note a DeprecationWarning, which I am still not happy with
   ----------------------------------------------------------------------
   Ran 769 tests in 82.757s

   OK

I am not convinced that test.py is suitable for running tests of 
non-core software;  your report suggests to me a bug in test.py.
Can you elaborate on what you think we could do in the CMF tests to
work around that problem?

> #10:    Not purging the existing setup seems to have some issues
> 
>     -> ?
> 
> How is not-purging supposed to work? Currently existing Actions are 
> deleted, reimporting raises errors.

Each import step is supposed to know whether "don't purge" is sensible 
for it. and what to do when purging.  Running the same import twice 
without purging is highly likely to create conflicts (the same actions 
will be created twice, etc).

In theory, "don't purge" will be useful when applying a profile as an 
"update" to an existing site;  for it to work cleanly, the steps in the 
profile need to be designed for that.

Tres.
-- 
===============================================================
Tres Seaver                                tseaver at zope.com
Zope Corporation      "Zope Dealers"       http://www.zope.com