differences.

When an integer too large to fit in a 32-bit integer was provided as
  a 32-bit-integer BTree key or value on 64-bit machines, an
  OverflowError was raised. Now a TypeError is raised.

non-standart ;) time zones.

Cleanup trailing whitespace in verbose stats output.

between logs and ints.

  entry, the cache could be left in a stage when there is data marked
  current that should be invalidated, leading to persistent conflict
  errors.

- Invalidations of object records in ZEO caches, where the
  invalidation transaction ids matched the cached transaction ids
  should have been ignored.

- Corrupted or invalid cache files prevented ZEO clients from
  starting. Now, bad cache files are moved aside.

Cache simulation, while not perfect, seems to be much more accurate
now than it was before.

The ZEO cache trace statistics and simulation scripts have been
given more descriptive names and moved to the ZEO scripts package.

than before).  It's possible that process shutdown after updating
lastTid but before invalidating the current record could explain some
problems we've seen on restarts. (I can't think of a sane way to test
this scenario.)

platforms led to undetected overflow errors. Now these cases cause
Overflow errors to be raised.

https://bugs.launchpad.net/zodb/+bug/143237

Updating blobs in save points could cause spurious "invalidations
out of order" errors.  https://bugs.launchpad.net/zodb/+bug/509801

(Thanks to Christian Zagrodnick for chasing this down.)

2.7. :(

created temporarily (not passed to the constructor).

in. When no changes are passed to the constructor, then they are
closed when the storage is closed.

Changed the behavior for closing changes when changes weren't passed
in. When no changes are passed to the constructor, then they are
closed when the storage is closed.

Fixed a test that wasn't testing what it though it was (or anything really).

This required using manuel to get the footnote
feature. Unfortunately, manuel imports zope.testing.doctest. :)
Hpefully, this will be fixed soon.

Updated the testhistoricalconnections.py tearDown to clear conflict
resolution class cache. The cache was causing tests to fail when tests
were run multiple times.