From David Wilcox, Fedora Product Manager
Winchester, MA This is the third in a series of updates on the status of Fedora 4.0 as we move from the recently launched Beta  to the Production Release. The updates are structured around the goals and activities outlined in the July-December 2014 Planning document , 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.
Read the current status update here: https://wiki.duraspace.org/display/FF/2014-08-08+Fedora+4.0+Status+Update.
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
1) Fedora 3.8
The Fedora 3.8 code is currently being reviewed by several Fedora developers. Once the code review process is complete, a release candidate branch will be created and the code will be tested prior to a production release.
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.
2) Acceptance Testing
Thanks to the efforts of the Fedora community, 9 additional sets of Fedora 4.0 Beta  test results have been submitted to the wiki , bringing the total up to 10 (out of 44 features in need of testing). This is great progress, though 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  (or just use the one-click-run application ), test out some features, and submit your results .
3) Beta Pilot Projects
The details of two beta pilot projects are have been posted to the wiki ; these projects will be refined as timelines and deliverables are set. Early discussions on two other potential beta pilots are also taking place, the details of which will be posted to the wiki as they become available. These projects will test a number of Fedora 4.0 features in a production-like environment over the course of a few months.
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 (email@example.com).
4) Technical Working Group
The Technical Working Group  will hold its first meeting on August 13, 2014. The agenda  has been posted to the wiki, and the minutes will be available following the meeting.
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.
5) 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  (Oct. 6-7)
— Fedora 4 training to take place Oct. 7
- Islandora Camp, Colorado (Oct. 13-16)
— Fedora 4 training to take place Oct. 16
- eResearch Australasia (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
• New opportunities for data modelling, metadata enhancement, and linked open data in Fedora 4
• 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 (firstname.lastname@example.org).