You are here

Block title
Block content

NOW AVAILABLE: Fedora 4.2.0 Release

From Andrew Woods, Technical Lead for Fedora, on behalf of the Fedora team.

Winchester, MA  The Fedora team is pleased to announce that Fedora 4.2.0 was released on May 19, 2015 and is now available.

The focus of the 4.2.0 release was twofold:

  • Establish an Audit Service

  • Create and exercise tooling for Fedora 3 to 4 migrations

Additionally, numerous bugs and housekeeping issues were addressed.

Note: The reason this release is 4.2.0 instead of 4.1.2 is because the required version of Java was upgraded to Java8 per the project policy [3].



Release Manager, Andrew Woods


Issue Reporters


Audit Service

  1. Establish framework for capturing internal and external events in an external triplestore

  2. Establish framework for persisting internal and external events within the repository

  3. Create Audit Service administrator documentation [4]

Fedora 3 to 4 Migration

  1. With the migration-utils utility [5], enable the following types of migration from Fedora 3 to Fedora 4

    1. Simple RDF datastreams

    2. Redirect datastreams

    3. External datastreams

    4. Datastream properties

    5. RDF properties in RELS-INT datastreams

    6. Legacy-FS FOXML

Fedora Java Client

  1. Update Fedora 4 Java Client library [6] to:

    1. Support property updates on Non-RDF Source Descriptions

    2. Support creation of Fedora 4 "external" content with "message/external-body" content-type

Java 8

  1. Update build machinery and projects for Java 8

Linked Data Platform

  1. Respond with 501 on client-provided Link header for LDPR creation

  2. NonRDFSources now have rdf:type ldp:NonRDFSource

Bugs and Housekeeping

  1. Bug: Creating a node in the web application through a proxy causes the baseURL to be set incorrectly

  2. Standardizing underlying libraries

  3. Updating ReadMe files

  4. Refactoring code

  5. Reducing leakage of JCR concepts

  6. Improve OSGi support