2005

FLOW3 1.1 beta 2 released

The FLOW3 team is pleased to announce the release of FLOW3 1.1 beta 2. About two weeks after the release of the first beta, we have now all features for FLOW3 1.1 in place and present this second beta for getting feedback from the FLOW3 community.

Compared to version 1.1.0 beta 1 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.

Upgrading from FLOW3 1.0

As already announced for beta 1, 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 1, only small changes should be needed to your codebase.

Beta and Stable Releases

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 contains all features, including the big new ones. The objective for this release is to also get feedback on the HTTP foundation, the localization and translation framework and all the other gems we put into 1.1. We will provide documentation for all of the new features so you know how to test and use them in your own projects. Once we are confident that 1.1 works equally fine for you like it does for us, we are ready for a stable 1.1 release.

That documentation is not yet ready, as lack of time made the team slower than we hoped. Since we now only have to fix some remaining issues, a clear focus on filling the documentation gaps will be possible until the release of the first release candidate.

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.