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

Compare with Current View Page History

« Previous Version 22 Next »

Release date: December 14th, 2018

We are proud to announce the release of Fedora 5.0.0.

Resources

Team

Release Manager

Major  development contributions

All Developers

Testers

Issue Reporters

Summary

The focus of this major release was to align the Fedora codebase with the Fedora API Specification.  While the code behind basic CRUD (Create, Retrieve, Update, and Delete) changed only incrementally from the previous major release (4.7.5),  Versioning and Access Control functionality underwent major refactorings.  294 JIRA issues were worked by fifteen developers over the last year on the core codebase alone.  In addition,  we also developed the Fedora API Test Suite which can be run against this release to verify compliance with the aforementioned specification.  Finally, the documentation underwent a full overhaul  with special attention to the modifications to the API changes, additions, deletions, deprecations, and configuration settings.  

Due to the significant changes to existing APIs Fedora 5.0.0 is not backwards compatible.  The Fedora Import Export Utility does not currently support upgrading data from Fedora 4 to Fedora 5. However adding upgrade support this utility is one of our top priorities for the first quarter of 2019

Deprecations

  • Pair Tree

Housekeeping and Bugs

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.


Outstanding issues slated for the 5.0.1 Bugfix release (To be released in the next month)


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