[Zodb-checkins] CVS: ZODB3 - NEWS.txt:1.17.2.13 ZEO-NEWS.txt:1.39.2.13

[Jeremy Hylton]

Update of /cvs-repository/ZODB3
In directory cvs.zope.org:/tmp/cvs-serv11738

Modified Files:
      Tag: ZODB3-3_1-branch
	NEWS.txt ZEO-NEWS.txt 
Log Message:
Update news files with dates and last minute fixes.


=== ZODB3/NEWS.txt 1.17.2.12 => 1.17.2.13 ===
--- ZODB3/NEWS.txt:1.17.2.12	Fri Nov 15 12:18:56 2002
+++ ZODB3/NEWS.txt	Mon Dec  9 18:38:08 2002
@@ -1,6 +1,6 @@
 What's new in ZODB3 3.1.1?
 =========================
-Release date: XX-Nov-2002
+Release date: 10-Dev-2002
 
 It was possible for earlier versions of ZODB to deadlock when using
 multiple storages.  If multiple transactions committed concurrently
@@ -23,14 +23,16 @@
 raises KeyError, as expected.
 
 The restore() implementation in FileStorage wrote incorrect
-backpointers for a few corner cases involving versions and undo.
-These specific bugs have been fixed and new test cases were added to
-cover them.
+backpointers for a few corner cases involving versions and undo.  It
+also failed if the backpointer pointed to a record that was before the
+pack time.  These specific bugs have been fixed and new test cases
+were added to cover them.
 
 A bug was fixed in conflict resolution that raised a NameError when a
 class involved in a conflict could not be loaded.  The bug did not
 affect correctness, but prevent ZODB from caching the fact that the
-class was unloadable.
+class was unloadable.  A related bug fix prevented spurious
+AttributeErrors when a class could not be loaded.
 
 The script Tools/zeopack.py was fixed to work with ZEO 2.  It was
 untested and had two silly bugs.


=== ZODB3/ZEO-NEWS.txt 1.39.2.12 => 1.39.2.13 ===
--- ZODB3/ZEO-NEWS.txt:1.39.2.12	Thu Nov 21 14:02:09 2002
+++ ZODB3/ZEO-NEWS.txt	Mon Dec  9 18:38:08 2002
@@ -1,8 +1,12 @@
 Revision History, Zope Enterprise Objects, version 2
 
-  ZEO 2.0.1 (2002/11/XX)
+  ZEO 2.0.1 (2002/12/10)
 
     The changes since the ZEO 2.0 release are:
+
+      - The logging code for client connection was improved in several
+        ways.  In particular, client connection and disconnection
+        messages include the server's address.
 
       - ClientCache.py: make some functions into methods; include the
         storage name in all log messages; append the storage name to