Release date: TBD, 2016
We are proud to announce the release of Fedora 4.6.0.
Resources
Team
Release Manager
- A. Soroka, the University of Virginia
Developers
A. Soroka, University of Virginia
- Aaron Birkland, Johns Hopkins University
Unknown User (acoburn), Amherst College
Aaron Elkiss, University of Michigan
- Andrew Woods, DuraSpace
- Benjamin Armintor, Columbia University
- Bethany Seeger, Amherst College
- Bill Branan, DuraSpace
- Esme Cowles, Princeton University
- Jared Whiklo, University of Manitoba
- Michael Durbin, University of Virginia
- Michael J. Giarlo, Stanford University
- Mirek Simek, University of Chemistry and Technology, Prague
- Mohamed Mohideen Abdul Rasheed, University of Maryland
- Nick Ruest, York University
- Peter Eichman, University of Maryland
Issue Reporters
- Dummy
Summary
The Fedora 4.6.0 release furthers several major objectives:
- Tighten the definition of the RESTful application programming interface (API)
- Improving the Versioning capability
- Re-establish performance test fixtures
- Improve durability with MySQL and PostgreSQL backends
- Fix bugs
Application Programming Interface
One of the technical priorities [3] of Fedora is to define a well-specified application programming interface (API) against which client applications can be written and future server-side implementations can be created. This Fedora API should be clear and detailed enough such that a corresponding technology compatibility kit [4] (TCK) would be able to indicate if any Fedora implementation fulfills or diverges from the specification. With this in mind, several issues were addressed in this release that clean up Fedora's RESTful interaction [5].
Versioning
This release includes several bug fixes related to versioning]:
Web Access Control
Performance
One of Fedora's perennial goals is "improved performance". With this as a focus, a Performance and Scalability working group [10] has progressed in the creation of repeatable, scripted tests that exercise and meter basic read/write operations. The objective of these tests is to reveal application bottlenecks and to track changes in performance as the reference Fedora implementation evolves.
Preservation
From a preservation perspective, this release includes support for alternative backend object stores to the default LevelDB. New configurations now exist for MySQL and PostgreSQL [11].
Housekeeping and Bugfixes
Numerous refactorings, bugfixes, and clean-up tasks were addressed in this release [12]: