[Zope-CMF] Re: RFC: CMF 1.5 Release Plan

[Gregoire Weber]

Hi!

>Tres Seaver wrote:
>>I would like to propose the following release plan for CMF 1.5:
>>  - Release CMF 1.5alpha early next week (likely Wednesday), and
>>    encourage    sumbissions to the CMF collector.
>>  - Have a CMF bug day next Friday (7/9) to close issues for the beta.
>>  - Release CMF 1.5beta ~Friday, 7/16.
>>  - Release CMF 1.5final ~Friday, 7/23.

+1


>1.) UID generator tool and references machinery
>
>Some backported code from Archetypes was checked in on the at_reference_backport branch, but I don't think this is ready to be merged. While there was consensus that tools like that should become part of CMF, there was no discussion about the best implementation.
>
>An alternative to the Archetypes code would be a solution based on
><http://cvs.sourceforge.net/viewcvs.py/collective/CMFUid/>,
>but I guess this should be discussed as part of the 1.6 roadmap discussion.

I could invest some amount of time in incorporating uid generation
and management into CMF (CMFUid is from me) and probably a relation
tool also.

The approach attaches a callable uid attribute to arbitrary objects. 
The mechanism to deal with copy&paste is given with the 
ICallableOpaqueItemWithHooks interface I added to CMF 1.5 earlier 
this year.

I'd really not go the road of mixin classes as the at_reference_backport 
branch proposes. 

How I'd like to proceed:

   I'd like to have a look at various uid (and reference) implementations 
   out in the field (AT, CPS?, others?) and then make a interface proposal
   before starting to implementation.

   I'd like to get that all doen before CMF 1.5beta1 is due. Depending on
   the duration and (dis)agreement of discussions and implementation.

Opinions?

Gregoire