Re: Backward compatibility (was Re: Announcing Newt DB, the amphibious database)
Jason Madden <[email protected]>
| Newsgroups | gmane.comp.web.zope.zodb |
|---|---|
| Message-ID | <[email protected]> |
> On Feb 23, 2017, at 09:51, Jim Fulton <[email protected]> wrote: > >> That same buildout also specifies BTrees = 4.4.0 (yay), *but* also transaction = 1.7.0 because, IIUC, the underlying Zope2 doesn't handle the unicode username/note requirement (yet; see https://github.com/zopefoundation/Zope/pull/105). That's a problem because ZODB 5 requires transaction >= 2.0.3. > > So this is merged, but not released? Yes. > Would it's release be sufficient for Plone? I don't think so, but I can't be sure. I've just been casually following the Plone 6 efforts and the sprint checkins and the corresponding PLIPs (https://github.com/plone/Products.CMFPlone/issues/1351). The main PLIP that has to do with ZODB 5 (https://github.com/plone/Products.CMFPlone/issues/1845) has been marked as closed, but it references at at least two other PRs besides the Zope PR, but they seem to be test issues. And of course the version pin updates; I don't know what the Plone policy is on version bumps like that in their stable release series. Jason -- You received this message because you are subscribed to the Google Groups "zodb" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.