Internal 3.5a1 release.

NEWS.txt

-What's new in ZODB3 3.5a0?
+What's new in ZODB3 3.5a2?
 ==========================
-Release date: DD-MMM-YYYY
+Release date: DD-MMM-2005
+
+Following is combined news from "internal releases" (to support ongoing
+Zope3 development).  These are the dates of the internal releases:
+
+- 3.5a1 10-Jun-2005
+
+
+Multi-database
+--------------
+
+- (3.5a1) Preliminary support for persistent cross-database references has
+  been added.  See ``ZODB/cross-database-references.txt`` for an
+  introduction.
 
 
 What's new in ZODB3 3.4?
 ========================
-Release date: MM-DDD-2005
+Release date: 09-Jun-2005
 
 Following is combined news from the "internal releases" (to support
 ongoing Zope 2.8 and Zope3 development) since the last public ZODB 3.4

README.txt

@@ -35,8 +35,8 @@ The Zope 2.8 release, and Zope3 releases, should be compatible with this
 version of ZODB.  Note that Zope 2.7 and higher includes ZEO, so this package
 should only be needed to run a ZEO server.
 
-ZEO servers and clients are wholly compatible among 3.3, 3.3.1 and 3.4: a ZEO
-client from any of those versions can talk with a ZEO server from any.
+ZEO servers and clients are wholly compatible among 3.3, 3.3.1, 3.4 and 3.5:
+a ZEO client from any of those versions can talk with a ZEO server from any.
 
 Trying to mix ZEO clients and servers from 3.3 or later from ZODB releases
 before 3.3 is much harder.   ZODB 3.3 introduced multiversion concurrency

doc/guide/zodb.tex

 \documentclass{howto}
 
 \title{ZODB/ZEO Programming Guide}
-\release{3.5a0}
+\release{3.5.0a1}
 \date{\today}
 
 \author{A.M.\ Kuchling}

setup.py

@@ -264,7 +264,7 @@ class MyDistribution(Distribution):
 doclines = __doc__.split("\n")
 
 setup(name="ZODB3",
-      version="3.5a0",
+      version="3.5.0a1",
       maintainer="Zope Corporation",
       maintainer_email="zodb-dev@zope.org",
       url = "http://www.zope.org/Wikis/ZODB",

src/ZEO/__init__.py

@@ -22,4 +22,4 @@ ZEO is now part of ZODB; ZODB's home on the web is
 """
 
 # The next line must use double quotes, so release.py recognizes it.
-version = "3.5a0"
+version = "3.5.0a1"

src/ZEO/version.txt

-3.5a0
+3.5.0a1

src/ZODB/__init__.py

@@ -13,7 +13,7 @@
 ##############################################################################
 
 # The next line must use double quotes, so release.py recognizes it.
-__version__ = "3.5a0"
+__version__ = "3.5.0a1"
 
 import sys
 import __builtin__

src/ZODB/cross-database-references.txt

@@ -2,7 +2,7 @@ Cross-Database References
 =========================
 
 Persistent references to objects in different databases within a
-multi-database are allowed.  
+multi-database are allowed.
 
 Lets set up a multi-database with 2 databases:
 
@@ -54,26 +54,26 @@ It isn't valid to create references outside a multi database:
     >>> tm.commit() # doctest: +NORMALIZE_WHITESPACE
     Traceback (most recent call last):
     ...
-    InvalidObjectReference: 
+    InvalidObjectReference:
     Attempt to store an object from a foreign database connection
 
 NOTE
 ----
 
-This implementation is incomplete.  It allows creatting and using
+This implementation is incomplete.  It allows creating and using
 cross-database references, however, there are a number of facilities
 missing:
 
 cross-database garbage collection
     Garbage collection is done on a database by database basis.
     If an object on a database only has references to it from other
-    databases, then the object will be garbage collected when it's
+    databases, then the object will be garbage collected when its
     database is packed.  The cross-database references to it will be
     broken.
 
 cross-database undo
     Undo is only applied to a single database.  Fixing this for
-    mutliple databases is going to be extremely difficult.  Undo
+    multiple databases is going to be extremely difficult.  Undo
     currently poses consistency problems, so it is not (or should not
     be) widely used.
 

src/ZODB/tests/testcrossdatabasereferences.py

 ##############################################################################
 #
-# Copyright (c) 2004 Zope Corporation and Contributors.
+# Copyright (c) 2005 Zope Corporation and Contributors.
 # All Rights Reserved.
 #
 # This software is subject to the provisions of the Zope Public License,