On Sun, 16 Apr 2006 19:41:38 +0200, Martin Aspeli
<optilude gmx.net> wrote:
> So ... what shall we do?
>
> - Break people who got it wrong in the past (it's
obviously a simple
> fix, but it may piss people off)?
>
> - Use immediate_view only if immediate_view is not
the same as
> default_view?
>
> - Live without this feature and admit we
misunderstood?
My vote goes to fixing it properly - and fix it in all
Collective products
+ telling the author that he needs to make a new release for
2.5. Or
postpone the actual fix to 3.0 and deprecate in 2.5, being
responsible and
all (but still doing the Collective fixes, of course).
It's a simple thing to fix via grep, so I think this is the
best way of
going about it. Adding more crazy behaviour here doesn't
make it better.
--
____________________________________________________________
_________
Alexander Limi · Chief Architect · Plone Solutions ·
Norway
Consulting · Training · Development · http://www.plonesolutio
ns.com
____________________________________________________________
_________
Plone Co-Founder · http://plone.org · Connecting
Content
Plone Foundation · http://plone.org/foundati
on · Protecting Plone
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking
scripting language
that extends applications into web and mobile media. Attend
the live webcast
and join the prime developer group breaking into this new
coding territory!
http://sel.as-us.falkag.net/
sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Archetypes-devel mailing list
Archetypes-devel lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/archet
ypes-devel
|