[Zope-CMF] Re: [dev] delete members: related changes and updated proposal

[Yuppie]

Hi!


seb bacon wrote:
> I guess that at the least, the CMF will continue to be relevant right up
> to and beyond Zope 3.0's release in (maybe?) September 2004; and
> possibly, the lack of a decent upgrade path in the months immediately
> following the release of Zope X3 will engender a long-lived Zope2-based
> fork, and the CMF will continue to develop on that basis.  I can imagine
> the latter scenario especially being driven by the Plone community.
> 
> Whatever happens, I don't think there's cause for putting off
> refactorings or the like.  The End is Not Nigh :-)

AFAIK there are already some long term customer projects based on X3 on 
the way. So Zope X3 will definitely come in 2004 and there will be at 
least a Zope 2.8 version including some backports from X3.

Looking at the history of CMF, there were about 2 releases per year and 
I don't expect the release cycle to speed up. That means we'll have an 
1.5 release at the end of this year and maybe an 1.6 release in 
summer/autumn 2004. After that there will be only maintenance releases 
or releases focused on migration.

You may have noticed that I don't think it's too late to work on CMF. 
But if we mark the CMFCore-member-folder-API as deprecated in CMF 1.5, 
the earliest release we could remove it would be CMF 1.6. And that's why 
I guess it's too late to start a refactoring like that.


Of course I might be wrong in some points.

Cheers,
	Yuppie