The following supporters have open issues assigned to them in this collector
(http://www.zope.org/Collectors/CMF).
Assigned and Open
jens
- "CachingPolicyManager: Support OFS.Cache.CacheManager",
[Accepted] http://www.zope.org/Collectors/CMF/408
- "CachingPolicyManager: Make Ma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have need of using GenericSetup 1.1 on an older Zope / Five (2.8.6,
1.0.3), and found I needed to patch around some BBB breakage in imports
/ ZCML. In particular:
=== Products/GenericSetup/utils.py 1.1 => 1.1.2.1 ===
- --- Products/GenericSetup/uti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28 Apr 2006, at 12:45, Tres Seaver wrote:
Any objections to landing it on the 1.1 branch, as well as the
trunk? I
don't recall that we had a specific Zope / Five version designated as
"minimum required version" for GenericSetup (as opposed to
Hi Tres!
Tres Seaver wrote:
I have need of using GenericSetup 1.1 on an older Zope / Five (2.8.6,
1.0.3), and found I needed to patch around some BBB breakage in imports
/ ZCML. In particular:
[patch]
Even after this patch, a number of the GenericSetup unit tests fail
(mostly, in the sub-p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yuppie wrote:
> Hi Tres!
>
>
> Tres Seaver wrote:
>
>> I have need of using GenericSetup 1.1 on an older Zope / Five (2.8.6,
>> 1.0.3), and found I needed to patch around some BBB breakage in imports
>> / ZCML. In particular:
>>
>> [patch]
>> Even
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28 Apr 2006, at 15:00, Tres Seaver wrote:
I'm not happy with adding BBB code for incomplete Five 1.0 support. I
even did consider to propose removing Zope 2.8 compatibility on
the trunk.
I can live with that on the trunk, but am hopeful that
Tres Seaver wrote:
yuppie wrote:
GenericSetup/DEPENDENCIES.txt says:
Zope >= 2.8.5
Five >= 1.2
Is upgrading to Five 1.2 no option for you?
I have a report that Five 1.2 breaks something else in this customer's
application, and didn't have time to track that down further. I may
look into t
