[ZODB-Dev] ZODB 3.2.4 release candidate 2 not released

[Tim Peters]

ZODB 3.2.4c2 was tested and tagged, but I'm not going to finish the release
process.  The intent is that ZODB 3.2.4 final will match the ZODB shipped
with Zope 2.7.3 final (whenever that happens).  Since the ZODB3 module is
shared with Zope under CVS, this version of ZODB has been released in Zope
2.7.3 pre-releases all along, and cutting a distinct 3.2.4c2 release apart
from Zope would consume time with no obvious payback.

If anyone in the community would like to volunteer to create and test Unix
and Windows tarballs/installers, and update the ZODB 3.2 download page, let
me know.

Else you can check it out from CVS via tag

    ZODB3-3-2-4c2

on the ZODB3 module at cvs.zope.org:/cvs-repository.

Here's the NEWS since 3.2.4c1 was released (on 07-Sep-2004):

What's new in ZODB3 3.2.4 release candidate 2?
==============================================
Release date: 20-Oct-2004

ZEO
---

- The encoding of RPC calls between server and client was being done
  with protocol 0 ("text mode") pickles, which could require sending
  four times as many bytes as necessary.  Protocol 1 pickles are used
  now.  Thanks to Andreas Jung for the diagnosis and cure.

- Collector 1541:  small changes to zrpc were backported from ZODB 3.3,
  in order to play nice with asyncore changes in Python 2.4.

ReadConflictError
-----------------

An explicit transaction ``abort()`` wasn't clearing connections' memory of
``ReadConflictErrors`` raised during the transaction, and so new changes to
objects that suffered ``ReadConflictError`` still couldn't be committed in
the new transaction either.  Thanks to Chris McDonough for the diagnosis
and a focused test case.

ConflictError
-------------

The undocumented ``get_old_serial()`` and ``get_new_serial()`` methods
were swapped (the first returned the new serial, and the second returned
the old serial).