Hyrax - Release Notes: Difference between revisions

From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
Line 7: Line 7:
* Tested and approved for Tomcat 1.6.x
* Tested and approved for Tomcat 1.6.x
* Improved Error Messaging.
* Improved Error Messaging.
* XSLT based directory and error pages allow site administrators to customize Hyrax for visual integration with existing sites. [http://docs.opendap.org/index.php/Hyrax_-_Customizing_Hyrax More Here]
* XSLT based directory and error pages allow site administrators to customize Hyrax for visual integration with existing sites. ([http://docs.opendap.org/index.php/Hyrax_-_Customizing_Hyrax More Here])
<br/>
<br/>
<br/>
<br/>

Revision as of 20:23, 28 February 2008

Release 1.4.0 TBD 2008

This release contains:

  • Bug fixes and feature additions
  • Significant speed improvements for large data transfers (Details Here and Here.)
  • Tested and approved for Tomcat 1.6.x
  • Improved Error Messaging.
  • XSLT based directory and error pages allow site administrators to customize Hyrax for visual integration with existing sites. (More Here)



Release 1.3.1 December 10, 2007

The 1.3.1 release is a bug fix release:

  • The memory footprint has been reduced to address issues on small or medium sized machines.
  • Binaries installed from the RPM packages now store run-time files where most system administrators expect them to be stored.


Release 1.3.0 November 14, 2007

This release includes:

  • Bug Fixes
  • Hyrax control script - Simplifies starting and stopping Hyrax when running the BES and the OLFS on the same machine.
  • Compression support: Unix compress (.Z) is now supported.
  • Signed distributions: Our software distributions are now signed using a public/private key pair.

See Public Key for more information.


Release 1.2.1 April 27, 2007

  • Improved support for compressed files: The support for compressed data files has been completely revamped to be more efficient and safer. The cache used for the decompressed files has also be completely re-implemented.
  • Bug fixes
  • These fixes address important security issues which were found in the BES software. Sites running Hyrax should upgrade as soon as practical.

Updated (21 May) the BES and OLFS (to versions 3.5.1 and 1.2.3, resp.) to include a fix for a transmission problem that affects some large 32 bit floating point arrays.


Release 1.2.0 April 23, 2007

Major changes made to the OLFS allow:

1. Support for multiple BES's: Data providers may configure a single Hyrax installation to work with multiple BES's.

2. The OLFS dispatch code has been refactored to allow 3rd party dispatch handlers to be added simply by modifying the configuration and adding the java class files to the Tomcat library directory.

Release 1.1 March 15, 2007

First full public release!

All known bugs have been fixed. Hyrax is ready!

Here's the stuff we did for this milestone.

Release beta-1.0.2 January 02, 2007

2nd beta release. As of this release the name is changed from Server4 to Hyrax.

This release features:

  • Bug fixes for tickets 767, 784, 789, and 793.
  • Partial logging implementation (Ticket 785)
  • Improved documentation regarding shared libraries. (Ticket 780)
  • The BES and and the data handlers come with test data and will work and serve data immediately after an install using the default configuration. (Ticket 764)


Release beta-1.4 - January 02, 2007

1st beta release.

This release adds support for:

  • HTTP/1.1 persistent connections
  • Improved OPeNDAP directory response.
  • Prototype SOAP Interface.
  • Server UUID on top level directory for improved web searchability
  • Persistent content (configurations, user supplied documents/web pages, etc.)
  • Improved internal efficency via BES client connection pooling.


Release 1.3 - September 26, 2006

This was an internal release.

This release adds support for:

  • HTTP/1.1 caching - Support for conditional GET using If-Modified-Since and If-Unmodified-Since headers.
  • Persistent Configurations - Now local configurations will not be destroyed when installing new versions of the software. Configurations are stored in the $CATALINA_HOME/content/opendap directory.
  • Advanced THREDDS catalogs - These require thoughtful modification of the catalog.xml file located in the persistent content/configuration directory.


Release 1.2 - February 24, 2006

This was an internal release.

This release adds simple THREDDS catalogs to the server. No special configuration is required, simply add /catalog.xml to the end of a URL that references a "collection" of data sets and a THREDDS catalog will be returned.


Release 1.1 - February 17, 2006

This was an internal release.

Represents the first prototype release of Hyrax. It implements the feature set for releases 1.0 and 1.1, along with a smattering of features due in coming releases. In particular prototype implementations exist for F-23 and F-24 from release 1.2. At the time of this writing the intended feature set is still growing.


Release 1.0 - January 15, 2006

This was an internal release.