Re: Backward compatibility (was Re: Announcing Newt DB, the amphibious database)
Jim Fulton <[email protected]>
| Newsgroups | gmane.comp.web.zope.zodb |
|---|---|
| Message-ID | <CAPDm-Fjti+BoiaQZy2F5Fci-WpWFefoVbEqks48teWSCryUy_A@mail.gmail.com> |
On Sat, Mar 25, 2017 at 1:47 PM, David Glick (Glick Software) < [email protected]> wrote: > On 3/25/17 1:41 PM, Jim Fulton wrote: > > > > On Sat, Mar 25, 2017 at 1:33 PM, David Glick (Glick Software) < > [email protected]> wrote: > >> On 3/25/17 1:23 PM, Jim Fulton wrote: >> >> >> >> On Fri, Mar 17, 2017 at 8:36 AM, Jim Fulton <[email protected]> wrote: >> ... >> >>> So is there anything more that needs to be done to make it easy (ideally >>> the default) for current Plone users to use current ZODB releases? >>> >> >> Sorry to nag. I know y'all are busy, but what does it take for Plone >> users to use up-to-date ZODB and Newt at this point? Do they need to do >> anything special? >> >> In theory an adventurous Plone 4.3 or 5.0 user could upgrade to ZODB 5 >> now by overriding the version pins in their buildout for ZODB, ZODB3, >> persistent, BTrees, and ZEO. I haven't had a chance to try this on a real >> project yet. >> > > Are the version pins part of the releases? Can there be a new release, at > least for 5 that has updated pins? I'm afraid that if Plone and ZODB5 are > compatible now, the compatibility will rot if it isn't used (especially in > CI). > > > Yeah, a Plone release includes a versions.cfg file with a known good set > of versions. Updating to a new major version of a significant dependency > sounds like too big of a change to make in a 5.0 bugfix release. It could > probably happen for Plone 5.1, > Please! :) 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.