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
Jens Vagelpohl wrote:
I sent an email about this a couple days ago. Basically, I'm down to
one failing unit test in CMFUid and have discovered that CMFUid is
basically broken in 2.0/trunk. I also sent an email on this issue to
the list, hoping that the developers who wrote CMFUid and lobbied ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25 Apr 2006, at 15:08, Chris Withers wrote:
Jens Vagelpohl wrote:
I sent an email about this a couple days ago. Basically, I'm down
to one failing unit test in CMFUid and have discovered that
CMFUid is basically broken in 2.0/trunk. I also s
Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25 Apr 2006, at 15:08, Chris Withers wrote:
Jens Vagelpohl wrote:
I sent an email about this a couple days ago. Basically, I'm down to
one failing unit test in CMFUid and have discovered that CMFUid is
basically broken i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25 Apr 2006, at 15:51, Florent Guillaume wrote:
How would people feel about deprecating it for 2.1 and removing
it in 2.3 if no-one steps up who wants it?
Well, I have my own opinion about that, but the course of action
depends mostly on those
Hi Jens. Z3 has it own uid facilities. I guess folks could pick this up
through five could they not? Its all moving in that direction in any case.
Regards
David
Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25 Apr 2006, at 15:51, Florent Guillaume wrote:
How would p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25 Apr 2006, at 16:33, David Pratt wrote:
Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25 Apr 2006, at 15:51, Florent Guillaume wrote:
How would people feel about deprecating it for 2.1 and removing
it in 2.3 if no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florent Guillaume wrote:
> Jens Vagelpohl wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>>
>> On 25 Apr 2006, at 15:08, Chris Withers wrote:
>>
>>> Jens Vagelpohl wrote:
>>>
> I sent an email about this a couple days ago. Basical
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Winkler wrote:
> On Mon, Apr 24, 2006 at 10:13:45PM +0100, Jens Vagelpohl wrote:
>
>>-BEGIN PGP SIGNED MESSAGE-
>>Hash: SHA1
>>
>>
Adding missing pieces to the Zope 3 integration puzzle which could
not make it into the 2.0 relea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25 Apr 2006, at 17:49, Tres Seaver wrote:
I believe the work which Philipp and I did at PyCon will land for Zope
2.10 / Five 1.4. Until then, we don't have any story for view
customization: sites which depend on such customization will need to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yuppie wrote:
> Hi Jens!
>
>
> Jens Vagelpohl wrote:
>
>> CMF 2.0.0 is now out the door and I have made some updates to the
>> roadmap document. Please take a look and give me some feedback on the
>> dates (well, the only dates we have set are the d
On Tue, 25 Apr 2006 16:33:01 +0100, David Pratt
<[EMAIL PROTECTED]> wrote:
Hi Jens. Z3 has it own uid facilities. I guess folks could pick this up
through five could they not? Its all moving in that direction in any
case.
Plone doesn't have UID, but Archetypes does. This is used primarily
On Tue, 25 Apr 2006 20:21:09 +0100, Martin Aspeli
<[EMAIL PROTECTED]> wrote:
On Tue, 25 Apr 2006 16:33:01 +0100, David Pratt
<[EMAIL PROTECTED]> wrote:
Hi Jens. Z3 has it own uid facilities. I guess folks could pick this up
through five could they not? Its all moving in that direction in
13 matches
Mail list logo
