PersistentMapping was inadvertently pickling volatile attributes (http://www.zope.org/Collectors/Zope/2052).

See http://www.zope.org/Collectors/Zope/2027.

replaced `x` with repr(x), and replaced apply(x, y) with x(*y)

For multiple undo to succeed, the undo operations have to be
performed in a specific order.  The order was not being retained
by ZODB and was instead semi-random (the order depended on the
id() function.)  Now undo operations (as well as all
ResourceManagers) are sorted by creation order.

in the second iteration

ZODB uses `buildsupport` now, not `zpkgsetup`.
Updating this info in PACKAGE.cfg is needed to
build a release tarball.

_ConnectionPool._reduce_size():  when forgetting a Connection
due to exceeding pool_size available connections, clear its
cache right away.  Because such a connection can never be in
the open state again, hanging on to resources in its cache is
just wasteful.  This was reported as "a problem" on zodb-dev
recently, although it's unclear how the poster got into a state
where it mattered so much.

New zdaemon.

_setstate():  An MVCC optimization was inadvertently disabled by
fixes for ZClasses.  Repaired.

Elsewhere, repaired English in comments.

NEWS.txt:  removed news from 3.6 and earlier.

Dmitry seems to have vanished :-(

Note that nailing the type of oid to str may allow some
thread simplifications in Connection._invalidated handling.
Thanks to Florent Guillaume for noticing!

  tools need to perform minimal logging configuration themselves. Changed
  the zeoup script to do so and thus enable it to emit error messages.

http://mail.zope.org/pipermail/zodb-dev/2005-March/008593.html

with zope.whatever librairies that might be installed on the Python
version used to launch these tests.

- no longer try to find pop and popitem on UserDict as all supported
  Python versions have them
- added a test for the default argument of pop()
- added a NEWS.txt entry about pop()

- added unit tests for persistend mapping

Testing from a checkout is different than testing from a
distribution now.  Explain the differences.  Removed the
business about fiddling PYTHONPATH, because it shouldn't
be needed (and isn't for me ;-)).

same file as ZODB/tests/testConnectionSavepoint.txt. Do we really need 
both?

some good documentation here; I added all those files as chapters to the 
Zope 3 apidoc.

deprecated in ZODB 3.4.  This should be fun ;-)

method of ZODBDatabase factories.  This gives apps
(like Zopes 2.9 and 3.2) a relatively clean way to
set up their multidatabases.  An earlier checkin
adding an optional new database_name key to
<zodb> sections.

This allows specifying part of what's needed for multidatabases
in a ZODB config file.  More to come.

docs