Release date: 04 February, 2015
We are proud to announce the release of Fedora 4.1.0
Resources
Team
Release Manager
Andrew Woods (DuraSpace)
Developers
- Unknown User (acoburn) (Amherst College)
- A. Soroka (University of Virginia)
- Andrew Woods (DuraSpace)
- Unknown User (escowles@ucsd.edu) (University of California, San Diego)
- Longshou Situ (University of California, San Diego)
- Michael Durbin (University of Virginia)
- Osman Din (Yale University)
- Peter Eichman (University of Maryland)
- Yinlin Chen (Virginia Tech)
Issue Reporters
- Unknown User (acoburn)
- A. Soroka
- Andrew Woods
- Unknown User (escowles@ucsd.edu)
- Evgeni Dimitrov
- Justin Coyne
- Michael Durbin
- Mohamed Mohideen Abdul Rasheed
- Peter Eichman
- Stefano Cossu
Summary
Note on release version number
There has been significant community discussion about the fact that the metaphorical "4.1" release of Fedora being the release targeting the features and tooling needed for upgrading from Fedora 3 to 4. However, the upgrade tooling is not a part of this current 4.1.0 release. The current 4.1.0 release includes some backwards incompatible changes that has motivated numbering this version as 4.1.0. Specifically, there were minor naming changes to some of the optional configuration properties (see descriptions below) as well as naming changes to some of the Fedora ontology terms (see descriptions below).
Updates
Ontology
- Standardized naming of OWL classes...
- Removed unused terms...
- Published "indexing" vocabulary...
Configuration properties
- Made property names consistent internally and across projects...
Performance
- Transaction memory leaks...
- Blank nodes now auto-created in a performant hierarchy...
Camel module
- Graduated fcrepo-camel into fully supported module, out of "labs"...
- Better support for:
- Deployment into OSGi...
- Fedora resource streaming...
- Dynamic Fedora transformations...
- Integration tests...
- Both Fuseki and Sesame triplestores...
- "Prefer" headers...
- HTTPS connections...
- Named graphs...
- Improved documentation and examples...
OAI Provider module
- Eliminated unnecessary repository querying logic...
- Allow administrators to manage repository descriptions in OAI responses...
All Issues
References
[1]
