[ZODB-Dev] ZODB 3.3 alpha 3 released

[Andreas Jung]

should be working now

--On Sonntag, 18. April 2004 4:17 Uhr -0400 Kapil Thangavelu 
<hazmat at objectrealms.net> wrote:

> could some with permissions on zope.org pls fix the workflow on this..
> as a logged in member to zope.org i get an insufficient privileges
> redirect when trying to go to
>
> http://zope.org/Products/ZODB3.3/
>
> although attaching /folder_contents to the url seems to work fine...
>
> -k
>
> On Sat, 2004-04-17 at 14:02, Jeremy Hylton wrote:
>> I'm pleased to announce the release of ZODB2 3.3 alpha 3. This release
>> includes support for new-style persistent classes and multi-version
>> concurrency control. It's an alpha release, so we could use feedback on
>> the new features and helping testing them.
>>
>> The 3.3a3 release requires Python 2.3. It contains the code that is
>> slated to be in Zope 2.8.  This version of ZODB supports Zope 2 and Zope
>> 3.
>>
>> You can download a source tarball or Windows installer from
>> http://zope.org/Products/ZODB3.3
>>
>> This release contains a lot of changes and improvements since the
>> previous alpha releases.  The transaction API and implementation have
>> been overhauled and the persistence API has seen some changes to
>> accommodate Zope 3.  New features include persistent weak references, an
>> add() method for ZODB connections, and explicit transaction manager
>> objects.
>>
>> The news file lists the changes in more detail:
>> http://zope.org/Products/ZODB3.3/NEWS.html
>>
>> The new features in 3.3 represent major changes to ZODB. Support for
>> new-style classes means that ZODB programmers can use the new class
>> features introduced in Python 2.2, like properties and descriptors. It
>> also means that ZODB no longer uses ExtensionClass, which caused many
>> subtle incompatibilities with other classes.
>>
>> The multi-version concurrency control feature represents the end of read
>> conflicts. If a transaction encounters a conflict, it reads older
>> revisions of the object rather than raising a ReadConflictError. This
>> feature allows read-only transactions to see a consistent view of the
>> database without need to handle read conflicts and restart the
>> transaction.
>>
>> I'd also like to include a personal note:  This is the last ZODB release
>> that I will be actively involved in.  I will be starting a new job next
>> month at Google in New York City.  I've enjoyed working with everyone in
>> the ZODB and Zope communities; I'll be looking forward to the ZODB 3.3
>> final release along with you.
>>
>> Enjoy!
>>
>> -- Jeremy Hylton <http://www.python.org/~jeremy/>
>>
>>
>> _______________________________________________
>> For more information about ZODB, see the ZODB Wiki:
>> http://www.zope.org/Wikis/ZODB/
>>
>> ZODB-Dev mailing list  -  ZODB-Dev at zope.org
>> http://mail.zope.org/mailman/listinfo/zodb-dev
>>
>
>
> _______________________________________________
> For more information about ZODB, see the ZODB Wiki:
> http://www.zope.org/Wikis/ZODB/
>
> ZODB-Dev mailing list  -  ZODB-Dev at zope.org
> http://mail.zope.org/mailman/listinfo/zodb-dev