Tres Seaver wrote:
> David Glick wrote:
>
>> How soon can we expect a CMF 2.2 release? Are there blockers, aside
>> from a final Zope 2.12 release? Ideally we'd like to make an alpha
>> release of Plone 4 around the beginning of October (right, Eric?)
>
> I don't know of any real blockers:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Glick wrote:
> How soon can we expect a CMF 2.2 release? Are there blockers, aside
> from a final Zope 2.12 release? Ideally we'd like to make an alpha
> release of Plone 4 around the beginning of October (right, Eric?)
I don't know of an
On Jul 9, 2009, at 11:15 AM, Charlie Clark wrote:
> As previously noted backwards compatability should be desirable but
> not at
> too high a price. CMF 2.2 contains a lot of changes not least the
> eggification and buildout support that stem largely from the changes
> in
> Zope trunk so it is
Am 05.07.2009, 17:38 Uhr, schrieb yuppie :
> 1.) Make Zope >= 2.12 required for CMF 2.2 and change all imports.
> 2.) Make Zope < 2.13 required for CMF 2.2.
> 3.) Add zope.app.component and zope.app.container to CMF dependencies.
> 4.) Re-add zope.app.component and zope.app.container to Zope 2 tru
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 5, 2009, at 16:47 , Tres Seaver wrote:
> I would change CMF 2.2 to import from the new locations, and require
> Zope >= 2.12: I can see no benefit in trying to straddle with 2.11,
> and
> Plone 4.0 is supposed to move to Zope 2.12 and CMF 2
Tres Seaver wrote:
> yuppie wrote:
>>
>> Possible solutions:
>> ---
>>
>> 1.) Make Zope >= 2.12 required for CMF 2.2 and change all imports.
>>
>> 2.) Make Zope < 2.13 required for CMF 2.2.
>>
>> 3.) Add zope.app.component and zope.app.container to CMF dependencies.
>>
>> 4.) Re-add
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yuppie wrote:
> Hi!
>
>
> zope.app.component and zope.app.container are no longer part of Zope 2
> trunk, but CMF currently has many imports from these two packages.
>
> All the code needed by CMF has been moved to new packages (zope.site,
> zope.
Hi!
zope.app.component and zope.app.container are no longer part of Zope 2
trunk, but CMF currently has many imports from these two packages.
All the code needed by CMF has been moved to new packages (zope.site,
zope.browser, zope.container) that are part of Zope 2 trunk, but they
are not par
