Martijn Faassen wrote:
> So I see two responses for Plone developers:
> * they know that they need new versions of zope.app.container and
> zope.app.component too and require people to upgrade those too. This
> might work fairly well, but does require the upgrade of more than just a
> *few* packages, with the increased risk of breakage.
Or we can manage this with known good sets and careful testing.
> * they try to ignore this issue (because they don't know or care) and
> things may continue to work. Perhaps nobody ever uses Container in Plone
> anyway, and in practice everything's just fine. Based on a lot of luck.
It's never going to be pretty, but it may be necessary given that the
innovation that's going to happen "further down the stack" seems to move
in an backwards-incompatible (or compatibility-challenge) direction.
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -