[Zodb-checkins] CVS: ZODB3 - NEWS.txt:1.21 README.txt:1.11 ZEO-NEWS.txt:1.42 setup.py:1.22

Jeremy Hylton jeremy@zope.com
Wed, 23 Oct 2002 15:07:06 -0400


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

Modified Files:
	NEWS.txt README.txt ZEO-NEWS.txt setup.py 
Log Message:
Frontport changes made on 3.1 release branch just prior to release.


=== ZODB3/NEWS.txt 1.20 => 1.21 ===
--- ZODB3/NEWS.txt:1.20	Fri Oct 18 08:44:45 2002
+++ ZODB3/NEWS.txt	Wed Oct 23 15:06:35 2002
@@ -1,10 +1,33 @@
-What's new in ZODB3 3.1 (final)?
+What's new in ZODB3 3.1 beta 3?
 ===============================
-Release date: XX-XXX-2002
+Release date: 18-Oct-2002
 
-Several improvements were made to zdaemon: the log messages were made
-more readable, a bug in signal forwarding was fixed, and a newline is
-now appended to the pidfile.
+A small extension was made to the iterator protocol.  The Record
+objects, which are returned by the per-transaction iterators, contain
+a new `data_txn` attribute.  It is None, unless the data contained in
+the record is a logical copy of an earlier transaction's data.  For
+example, when transactional undo modifies an object, it creates a
+logical copy of the earlier transaction's data.  Note that this
+provide a stronger statement about consistency than whether the data
+in two records is the same; it's possible for two different updates to
+an object to coincidentally have the same data.
+
+A few bugs were fixed.
+
+The setattr slot of the cPersistence C API was being initialized to
+NULL.  The proper initialization was restored, preventing crashes in
+some applications with C extensions that used persistence.
+
+The return value of TimeStamp's __cmp__ method was clipped to return
+only 1, 0, -1.
+
+The restore() method was fixed to write a valid backpointer if the
+update being restored is in a version.
+
+Several bugs and improvements were made to zdaemon, which can be used
+to run the ZEO server.  The parent now forwards signals to the child
+as intended.  Pidfile handling was improved and the trailing newline
+was omitted.
 
 What's new in ZODB3 3.1 beta 2?
 ===============================


=== ZODB3/README.txt 1.10 => 1.11 ===
--- ZODB3/README.txt:1.10	Mon Oct  7 12:52:07 2002
+++ ZODB3/README.txt	Wed Oct 23 15:06:35 2002
@@ -1,4 +1,4 @@
-ZODB3 3.1 beta 2
+ZODB3 3.1 beta 3
 ================
 
 Please see the LICENSE.txt file for terms and conditions.
@@ -18,7 +18,7 @@
 
 ZODB3 is known to work with Python 2.1.3, 2.2, and the
 not-yet-released 2.3.  For best results, we recommend using Python
-2.1.3 or Python 2.2.2.  Note that 2.1.1 does *not* work.
+2.1.3 or Python 2.2.2.  Note that 2.2.1 does not work.
 
 Our primary development platform is Linux, but we also test on Windows
 2000 and 98.  The test suite should pass without error on all of these
@@ -49,10 +49,6 @@
 use at least Berkeley 4.0.14 and PyBSDDB 3.4.0.  See the
 `bsddb3Storage/README` file for details.
 
-There is a bug in Python 2.2.1 that causes crashes on some platforms.
-If you are using Python 2.2.1, you should recompile Python with the patch in
-`typeobject.patch` applied.
-
 Installation
 ------------
 
@@ -77,12 +73,12 @@
 You can test this by cd'ing to your home directory and typing the
 following commands::
 
-    Python 2.2.1 (#1, Jun 28 2002, 15:05:26) 
+    Python 2.2.2 (#1, Oct 18 2002, 15:34:34) 
     [GCC 2.95.3 19991030 (prerelease)] on linux2
     Type "help", "copyright", "credits" or "license" for more information.
     >>> import ZODB
     >>> ZODB.__version__
-    '3.1b2'
+    '3.1b3'
 
 To install ZODB3 using ZEO version 1 instead of version 2, pass the 
 ``--with-zeo1`` argument to setup.py when you build and install::
@@ -106,7 +102,7 @@
 third-party libraries.  On Windows, the tests can take much longer to
 execute::
 
-    Ran 975 tests in 161.
+    Ran 859 tests in 153.277s
 
     OK
 
@@ -180,8 +176,8 @@
 Bugs and Patches
 ----------------
 
-For now, you can submit bug reports and patches on Andrew's
-ZODB SourceForge project at:
+You can submit bug reports and patches on Andrew's ZODB SourceForge
+project at:
 
     http://sourceforge.net/tracker/?group_id=15628
 


=== ZODB3/ZEO-NEWS.txt 1.41 => 1.42 ===
--- ZODB3/ZEO-NEWS.txt:1.41	Fri Oct  4 20:31:44 2002
+++ ZODB3/ZEO-NEWS.txt	Wed Oct 23 15:06:35 2002
@@ -4,7 +4,25 @@
 
     The changes since the ZEO 2.0b2 release are:
 
-      - XXX
+      - Changed signal handling in start.py script.  The start script
+        was changed to respond to signals in the same manner as Zope.
+        See Doc/ZEO/SIGNALS.txt (new).
+
+      - Changed pidfile policy in start.py script.  The start script
+        only writes a single pid to the pidfile; when using zdaemon,
+        this is the zdaemon process's pid (which passes signals on to
+        the actual storage server).  Also, the pidfile is deleted upon
+        completion of the server's main loop.  (Only this latter
+        change was also applied to ZEO1/start.py.)
+
+      - The start script now chdir's into the var directory, to give a
+        predictable place for core dumps.
+
+      - The stats.py and simul.py script now skip suspect broken
+        records; this makes for a more robust trace analysis.
+
+      - Some files had their RCS Id removed from docstrings; this was
+        used only sporadically.
 
   ZEO 2.0 beta 2 (2002/10/04)
 


=== ZODB3/setup.py 1.21 => 1.22 ===
--- ZODB3/setup.py:1.21	Fri Oct  4 20:38:12 2002
+++ ZODB3/setup.py	Wed Oct 23 15:06:35 2002
@@ -176,7 +176,7 @@
 doclines = __doc__.split("\n")
 
 setup(name="ZODB3",
-      version="3.1b2",
+      version="3.1b3",
       maintainer="Zope Corporation",
       maintainer_email="zodb-dev@zope.org",
       url = "http://www.zope.org/Wikis/ZODB/FrontPage",