Backward compatibility (was Re: Announcing Newt DB, the amphibious database)

On Thu, Feb 23, 2017 at 10:22 AM, Jason Madden <[email protected]
> wrote:

>
> > On Feb 23, 2017, at 08:47, Jim Fulton <[email protected]> wrote:
> >
> >> This is my queue to move to Plone 5. Thanks for the nudge.
> >
> > Does Plone 5 support ZODB 5/Relstorage 2?
>
> Out of the box, no.
>
> The buildout for Plone 5.1 (https://github.com/plone/
> buildout.coredev/blob/5.1/versions.cfg) points to http://dist.plone.org/
> versions/zope-2-13-26-versions.cfg which still specifies ZODB3 = 3.10.7.
>
> 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?  Would it's release be sufficient for
Plone?


>
> One might be able to cobble something together that works, though.
>

Sigh.  OK, going forward, I want to stop doing things that breaks
significant users of ZODB without a clear and straightforward way to move
them forward.

I'm willing to backtrack on some of the transaction changes to accommodate
a current stable release of Plone. It would be great if someone helped me
figure out what needs to be backed up.

I'm going to bring this up on the transaction mailing list.

Jim

-- 
Jim Fulton
http://jimfulton.info

-- 
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.