ZODB 3.2.2 (final) released
I'm pleased to announce the release of ZODB 3.2.2 (final). This is the version of ZODB that will ship with Zope 2.7.1 (final). Upgrading to ZODB 3.2.2 is strongly recommended for all users, and is critical for sites running ZRS. You can download a source tarball or Windows installer from: http://zope.org/Products/ZODB3.2 As promised with the ZODB 3.2.2b1 release last week, the tests for the unsupported Berkeley-based storages are now disabled in 3.2.2. In addition, a small but critical bug in FileStorage.restore() was identified and repaired. This bug didn't affect the Zope core, but is critical for sites running ZRS. See the news file for more detail: http://zope.org/Products/ZODB3.3/NEWS Note that ZODB 3.2.2 does not support Zope X3 (Zope 3 requires ZODB 3.3 -- as will Zope 2.8).
I'm pleased to announce the release of ZODB 3.2.3. This corresponds to the ZODB (and ZEO) that shipped with Zope 2.7.2. Upgrading to ZODB 3.2.3 is recommended for all users. You can download a source tarball or Windows installer from: http://zope.org/Products/ZODB3.2 This is a pure bugfix release. The most prominent fix since ZOBD 3.2.2 is in ZEO's treatment of temporary cache files. See the news file for details: http://zope.org/Products/ZODB3.2/NEWS Note that ZODB 3.2.3 does not support Zope X3 (Zope 3 requires ZODB 3.3 -- as will Zope 2.8).
I'm pleased to announce the release of ZODB 3.3b2. This corresponds to the ZODB (and ZEO) that will ship with ZopeX3-3.0.0b2. Note that ZODB 3.3b2 cannot be used with any released version of Zope2. You can download a source tarball or Windows installer from: http://zope.org/Products/ZODB3.3/ This is a pure bugfix release. See the news file for details: http://zope.org/Products/ZODB3.3/NEWS.html
I'm pleased to announce the release of ZODB 3.2.4c1. This corresponds to the ZODB (and ZEO) that we intend to ship with Zope 2.7.3. You can download a source tarball or Windows installer from: http://zope.org/Products/ZODB3.2 3.2.4c1 incorporates several small bugfixes, and one crucial new behavior: it's incorrect to attempt to close a connection when objects from that connection are still in a modified state. When an application modifies, or creates, a persistent object, it should always abort() or commit() the transaction before closing the connection. However, ZODB didn't enforce this, and applications that closed a connection with pending modifications could get into catastrophic trouble as a result. For example, it was easy to create dangling references in the database this way (references to objects that don't exist, resulting in POSKeyError upon an attempt to load them). ZODB 3.2.4c1 raises the new ConnectionStateError if an attempt to cloase a connection with pending modifications is made. See the news file for details: http://zope.org/Products/ZODB3.2/NEWS The intent is that 3.2.4c1 will be released again as 3.2.4 (final) shortly before the Zope 2.7.3 release. Note that ZODB 3.2.4c1 does not support Zope 2.7.2, because the Zope 2.7.2 publishing subsystem is an example of application code that didn't always finish a transaction before closing connections. ZODB 3.2.4c1 can be used with the current Zope Zope-2_7-branch branch. Note that ZODB 3.2.4c1 does not support Zope X3 (Zope 3 requires ZODB 3.3 -- as will Zope 2.8).
participants (1)
-
Tim Peters