From David Wilcox, Fedora Product Manager
Winchester, MA This is the fourth 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.
Below is a link to the current status update (also included in full in the body of this email): https://wiki.duraspace.org/display/FF/2014-08-22+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) NEW: Fedora 4.0-Beta-2
The Fedora 4 team is proud to announce the second Beta release of Fedora 4.0. Full release notes are available , and highlights include:
- Transparent JCR/XML file system export 
- Reviewed and published Fedora 4 RDF ontology
- Clustering for high-availability use cases 
- Performance testing for large numbers of files 
Early testing by members of the Hydra community revealed a bug in Fedora 4.0-Beta-2 that has already been resolved . A fixed Fedora 4.0-Beta-3 release will be available later this week.
2) Fedora 3.8
The Fedora 3.8.0 code review process is now complete, and a test plan  has been created. We are asking Fedora community members to download the release candidate , follow the test plan, and submit your results. Once testing is complete, a production Fedora 3.8.0 will be released.
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 , 2 additional sets of Fedora 4.0 Beta  test results have been submitted to the wiki , bringing the total up to 12 (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  (or just use the one-click-run application ), test out some features, and submit your results .
4) Beta Pilot Projects
We are making progress with three Beta Pilot projects, each of which you can read about on the wiki . These projects will test a number of Fedora 4.0 features in a production-like environment over the course of a few months. Each of these projects will be showcased in a short webinar series this Fall - details will be available soon.
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 (firstname.lastname@example.org).
5) Technical Working Group
The Technical Working Group  held its first meeting on August 13, 2014. The minutes are available on the wiki . The group established an approach for addressing the initial objectives, and posted an architecture diagram  for discussion. The second meeting was held on August 20, 2014. This meeting focused on reviewing the areas of assessment , walking through the architecture diagram, and reviewing the performance testing summary . The full meeting minutes are available on the wiki .
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  (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 (email@example.com).