Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • REST API Validation failure response codes changed to 400. If a REST API management operation results in a validation failure (e.g. ingest FOXML validation, validation failure via the DOObjectValidator module) the HTTP response code is now 400. Previously Fedora reported a generic Server Failure 500 response code. The response body indicates the nature of the validation error.
  • *(populate metadata to akubra/hints api)
  • *upstream/sso

You are encouraged to download this new release and give it a spin. Please let us have your comments and feedback via the mailing lists, and of course please let us know of any problems you discover.

...

Acknowledgments

Many thanks to all of those everyone who contributed to this release. In particular, thanks go to Jiri Kremser, a doctoral student at Masaryk University in the Czech Republic, for his work on the Google Summer of Code project.

Fedora 3.5 Release Notes

Release Date: August 18, 2011:

We are proud to announce the release of Fedora 3.5. Although a minor release, this version includes a number of exciting new features and bug fixes that make Fedora an ever more compelling repository platform.

You are encouraged to download this new release and give it a spin. Please let us have your comments and feedback via the mailing lists, and of course please let us know of any problems you discover.

Some of the important new features are:

...

.

...

Note
titleTomcat Compatibility

Tomcat 5.5 and earlier are no longer supported. This release has been extensively tested with Tomcat 6.0.x, and is also known to work with Tomcat 7.0.x

...

Note
titleREST API

As part of ongoing cleanup efforts, REST API responses have been fixed so that they are now fully compliant with their declared schema. This means that some responses might be slightly different when compared to those from earlier releases. For more information, see the overarching issue in Jira

Note
titleTomcat memory leak detection

Starting with Tomcat 6.0.24 (the bundled version of Tomcat included in this release is 6.0.29), Tomcat logs messages to indicate potential memory leaks. You may notice a number of SEVERE messages logged when Tomcat is stopped as a consequence of this new Tomcat behavior. FCREPO-969 has been logged to track these and address these where they lie within Fedora code.

For a detailed list of features and bugfixes comprising this release see the tables below.

Acknowledgments

...


Features and Improvements

...