You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Release date: TBA

We are proud to announce the release of Fedora 4.7.0.

Resources

Team

Release Manager

Developers

Issue Reporters

Summary

The Fedora 4.7.0 release furthers several major objectives:

  • Upgrade to Modeshape 5.0.0 Final 
  • Fedora Export/Import service tools
  • Tighten the definition of the RESTful application programming interface (API)
  • Replace legacy transform service with more powerful LDPath service
  • Fix bugs

This release will be the last release built against a version of Modeshape that uses Infinispan for data storage.

This release is a major release (i.e. 4.7.0 instead of 4.6.1) because of the upgrade to Modeshape 5 which no longer uses Infinispan. This requires a complete export and import of repository contents.

Changes

 

Modeshape 5 upgrade

The Modeshape 5 implementation removes it's use of Infinispan. This change requires that the data be imported into a Fedora 4.7.0 repository instead of replacing one version with another.

Replace fcrepo-transform with a LDPath service

The extension module fcrepo-transform is not included in the 4.7.0 release of Fedora. This module was used to transform RDF resources into JSON using programs based on LDPath. The functionality provided by fcrepo-transform is now available in the fcrepo-ldpath component of the fcrepo-camel-toolbox project.

More information about using the fcrepo-ldpath component is available in the project README: https://github.com/fcrepo4-exts/fcrepo-camel-toolbox/tree/master/fcrepo-ldpath

Additional information about LDPath can be found on the Marmotta website: http://marmotta.apache.org/ldpath/language.html

Housekeeping and Bugfixes

Numerous refactorings, bugfixes, and clean-up tasks were addressed in this release:

key summary type created updated due assignee reporter priority status resolution

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Complete Listing of Resolved Tickets

key summary type created updated due assignee reporter priority status resolution

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  • No labels