The FLOW3 team announces the release of FLOW3 1.1 beta 3. After the release of the second beta, we have fixed a number of issues and present this third beta for getting feedback from the FLOW3 community before a release candidate.
Compared to version 1.1.0 beta 2 it fixes more than 25 bugs and other issues. A changelog can be found in the documentation and is also linked to on the website in the download section.
The FLOW3 documentation has been updated since the second beta, but sadly it is still not complete - read on if you want to help out with this!
Upgrading from FLOW3 1.0
As already announced for the previous beta releases, FLOW3 1.1 contains some breaking changes and is not 100% backwards compatible. Please use the new code migration tool to automatically adjust your code to fit the most important API changes. And for the few parts it can't refactor you just follow the detailed upgrade instructions.
If you upgrade from beta 2, only small changes should be needed to your configuration (if at all).
Beta and Stable Releases
With this release of a third beta we leave our planned track - only two beta releases were expected. But we still have a number of open issues that would make calling this one a release candidate in the true sense a soap opera episode…
We plan to release two beta versions in total, followed by the stable release of FLOW3 1.1. If necessary, we'd also release additional betas or adjust the timeline in order to meet our quality standards. Both planned beta releases have a specific goal:
FLOW3 1.1 beta 1 contained all improvements we want to see in the final version. The goal for that release was to get feedback on the compatibility and stability: does your project still work fine after following our upgrade instructions? What did we miss? Although the first beta contained most of the code of the new major features (HTTP, I18N, content security, more speed ...), those features were not fully documented yet.
FLOW3 1.1 beta 2 contained all features, including the big new ones. The objective for that release was to also get feedback on the HTTP foundation, the localization and translation framework and all the other gems we put into 1.1.
The third beta released today gives us some more time to iron out remaining issues and gather more feedback.
Share Your Insights
At this point we’d like to invite you to upgrade existing projects or start new ones based on 1.1. Don’t use it in production yet, but please do share your insights and possible problems you might face. Please refer to the upgrading instructions and add your own findings to the related discussion page.
The planned release date for FLOW3 1.1 RC 1 is now June 26th. We hope you enjoy the third beta until then.