[OpenAFS-announce] OpenAFS 1.5.36 released (Production Version for Windows; Test Version for other platforms)

[Derrick J Brashear]

1.5.36 is the recommended production-ready release of OpenAFS for
Microsoft Windows users.  It supports all Microsoft Windows operating
systems from Windows 2000 through Windows Vista SP1 and Windows Server 2008 
including both 32-bit and 64-bit architectures.  The 1.5.36 release
continues the recent efforts at optimizing the performance of the
Windows client and improving its scalability.

For UNIX, Linux, and MacOS X the recommend production-ready release of
OpenAFS is 1.4.7.  The 1.5.36 Windows client is fully compatible with
all AFS server versions.

Please visit http://www.openafs.org/windows.html for up to date
information on the status of the OpenAFS for Windows client.

Windows:

* Fix a cm_buf_t reference count leak when attempts to write
  dirty buffers to the file server from within cm_IncrSyncer()
  fail.

* Prevent udebug from crashing.

* Another VNOVNODE issue fixed.  When writing a dirty buffer
   to the file server, if VNOVNODE is received, mark all buffers
   as invalid without further attempts to contact the file server.

All platforms:

* Rx optimizations now attempt to deal with high latency WANs.

* Fileserver avoids a potential infinite loop when a client relinquishes
   an address.

* Fileserver large setting now configures more threads.

* Fileserver properly registers uuids of new clients.

* Client will not wait infinitely for a server which is not providing data.
   Additional servers will be polled without marking the server which is
   not providing data down.

* Ubik servers do not improperly hide updates from clients.

* vos move will not erroneously unlock locked vldb entries on failure.

* Fileservers reserve enough file descriptors such that each thread can
   cache one to avoid spurious errors.

Source code and binaries can be downloaded from

    http://www.openafs.org/windows.html
    http://www.openafs.org/release/openafs-1.5.36.html

Please send reports of successful deployments to
openafs-info@openafs.org and report problems to openafs-bugs@openafs.org.

Derrick Brashear
for the OpenAFS Gatekeepers