You are here

Block title
Block content

Update 5: Beta Pilot Projects Set to Kick-Off

From David Wilcox, Fedora Product Manager
Winchester, MA This is the fifth in a series of updates on the status of Fedora 4.0 as we move from the Beta [1] to the Production Release. The updates are structured around the goals and activities outlined in the July-December 2014 Planning document [2], and will serve to both demonstrate progress and call for action as needed. New information since the last status update is highlighted in bold text.
All the activities outlined in this status update support the following short-term goals for July-December 2014:
• Release Fedora 3.8 and communicate the End-of-life (EOL) status of the Fedora 3.x line
• Release Fedora 4.0-production
• Ensure Fedora 4 provides a strong foundation for the community's technical needs
• Increase developer and user community
NEW: Fedora 4.0 Production Requirements
Several requirements need to be satisfied before we can release Fedora 4.0 into Production. This section summarizes the current status of these requirements - further details can be found in the updates below.
1) Acceptance Tests
16 of 44 Completed [3]
2) Beta Pilots
Art Institute of Chicago [4]
Project Defined——Agreement Established——Testing Begun——Outcomes Reported
Step: 1 of 4
University of California San Diego [5]
Project Defined——Agreement Established——Testing Begun——Outcomes Reported
Step: 1 of 4
Pennsylvania State University [6]
Project Defined——Agreement Established——Testing Begun——Outcomes Reported
Step: 1 of 4
1) NEW: Fedora 4.0-Beta-3
Fedora 4.0 Beta 3 [7] introduces a fix for a bug that surfaced in Fedora 4.0 Beta 2 [8]. As this is the only major change between Beta 2 and Beta 3, the Fedora 4.0 Beta 2 highlights are listed below:
- Transparent JCR/XML file system export [9]
- Reviewed and published Fedora 4 RDF ontology
- Clustering for high-availability use cases [13]
- Performance testing for large numbers of files [14]
2) Fedora 3.8
A number of Fedora community members have contributed to Fedora 3.8.0 release testing [15], but several tests still need to be run before we can package a production release. We are asking Fedora community members to download the release candidate [16], follow the test plan, and submit your results.
Fedora 3.8 will be the final release in the Fedora 3.x line (aside from the unlikely need for security patches). All community and development energy is now shifting to Fedora 4, so support for Fedora 3.x will gradually decrease as more Fedora users and developers transition to the new platform. 
3) Acceptance Testing
Since the last Fedora 4.0 Status Update [17], 4 additional sets of Fedora 4.0 Beta [18] test results have been submitted to the wiki [19], bringing the total up to 16 (out of 44 features in need of testing). We are making progress, but we still need to test the remaining features before we can release the production version of Fedora 4.0. Please take some time to install the Fedora 4.0 Beta [20] (or just use the one-click-run application [21]), test out some features, and submit your results [22].
4) Beta Pilot Projects
Details for the three current Beta Pilot projects continue to be added to the wiki [23], and the projects themselves are starting to kick off. A community meeting to discuss the Pennsylvania State University project was held recently, the details of which are available on the wiki [24].
Beta Pilot Projects represent a larger commitment of time and resources than acceptance tests, but they also present an opportunity to test real institutional use cases with Fedora 4.0, with added support from DuraSpace and the Fedora community. We will continue to update the community on the status of beta pilot projects as we firm up the details and bring new institutions on board. If your institution is interested in participating, please contact David Wilcox (
5) Technical Working Group
The Technical Working Group [25] held its third meeting on August 27, 2014. The minutes are available on the wiki [26]. Action items included drafting a REST-API spec [27] and putting together some performance testing scenarios [28]. A fourth meeting was held on September 3, 2014 [29], which included discussions on the approach and details around the REST-API spec and a plan for an enhanced performance testing framework.
The group's first task will be to review Fedora 4.0 Beta from a hands-on, technical perspective to identify any questions or concerns about Fedora 4.0 architecture in the context of the project’s goals, objectives, and use cases. The group will produce a report that will include recommendations for future development, architectural direction, and future investigation.
6) Fedora 4 Training
Planning and curriculum development for Fedora 4 training is under way, and several one-day training events have been scheduled for October, 2014:
- Washington, DC Fedora User Group Meeting [30] (Oct. 6-7)
— Fedora 4 training to take place Oct. 7
- Islandora Camp, Colorado [31] (Oct. 13-16)
— Fedora 4 training to take place Oct. 16
- eResearch Australasia [32] (Oct. 27-31)
— 'Fedora 4 Down Under' workshop to take place Oct. 31
Registration for the Washington, DC and Denver, CO events is free, while the workshop in Melbourne, AU costs $50 (generously subsidized by the University of New South Wales - the normal rate charged by the conference is $185). The agendas for these events are still under development, but may include such topics as:
- Fedora 4 feature overview
- Fedora 3 to Fedora 4 migration planning
- Fedora 4 for Administrators
- Getting started as a Fedora 4 developer
Further information on these events will be posted to the wiki and the mailing list as we finalize the agendas and develop training materials. If you are interested in helping out with planning and and organizing training events, please contact David Wilcox (