A short excerpt from an email discussing the 1.0 beta 2 release
Jim and Barry talked it over yesterday, and agreed that it's time to make a 1.0 beta 2 release of Berkeley storage. Here's the proposal for how that will happen logistically. We still haven't decided quite where to make the announcements, but the release will be posted here
First, I'm going to rearrange the cvs directory in bsddb3Storage to be more distutils friendly. This means:
- adding a subdirectory bsddb3Storage inside Packages/bsddb3Storage
- copying the ,v files in the repository into this new subdir, for the
following files:
BerkeleyBase.py CommitLog.py Full.py Minimal.py MinimalReplicated.py Packless.py __init__.py base.py
Then I'm going to "cvs remove" those files from the top level directory. This means we'll retain all the useful cvs history, but in end effect, have the source code inside a package named bsddb3Storage.
- I will leave LICENSE at the top directory, add a README, a NEWS file, a MANIFEST, and a setup.py file so that bsddb3Storage can be installed via distutils.
- Create a tests subdir under the bsddb3Storage, and copy all the ,v files from test to bsddb3Storage/tests, then cvs remove them from the test directory. bsddb3Storage/tests will be made into a Python package so that you could "import bsddb3Storage.tests.ZODBTestBase?".
- Create a docs subdir, into which I will do the ,v dance for FullImplementation.txt, MinimalImplementation.txt, PacklessImplementation.txt, PacklessReadme.txt, TransactionStrategy.txt, notes, custom_zodb.sample.
- I'm going to write an docs/INSTALL file to describe how to install and use Packless.py, Minimal.py, and Full.py in Zope.
- Run "python setup.py sdist" to create a source distribution and make that available here.
I think this will be good enough for the first beta release. Subsequent releases will be aimed at: adding reference counting and gc to Minimal so as to get rid of pack(). At that point, and assuming we're schema-compatible with Packless, we can recommend Minimal over Packless; integrate and test GC for Full.py -- we need to figure out how to include the StorageGC stuff into the Berkeley distro, or conditionalize its use.
- bwarsaw (Jun 14, 2001 4:59 pm; Comment #1)
- We've revised what will be in the 1.0 release for Berkeley storage. At this point we've taken GC support off the table for this release. Full GC support, as well as more flexible packing policies will be added in subsequent releases. I'm also not going to work on Minimal storage for this release; the demand has been nil.
Still left to do before the 1.0 final release for Berkeley: support of application level conflict resolution.