Roadmap & Missing Features for FLOW3 1.0 Beta 1

The next release of FLOW3 will be 1.0 beta 1 – that's no big news anymore. However, as we had to adjust the original schedule, you might ask yourself when the first beta version will be available. In order to get a realistic release date, we now ask for feedback by those who already gathered experience with the current Git master version of FLOW3.

Direct work on the FLOW3 feature set had to take a back seat for a while as we were quite busy with the development of TYPO3 5.0 and the launch of the T3CON11 website. Both projects were very helpful for finding the weak spots in the current FLOW3 alpha and identify some API changes and missing features we'd like to see in the first beta release.

The work on TYPO3 continues to be very intensive over the next weeks, but since some companies and individuals already started using FLOW3 for customer projects we don't want to unnecessarily postpone the FLOW3 final. Today I updated the roadmap for the FLOW3 Base distribution and attached some tentative dates to the next planned versions. Please don't nail us on June 17th for the first beta release – we're aiming for it, but a few factors can still change the date.

In the FLOW3 mailing list I sent a call for feedback. I'd like to ask those who are familiar with the current (not yet released) version of FLOW3, what features, concepts, API changes are still missing for 1.0 beta 1. And "beta" from my understanding means that basically all features we plan for the final release are there, API's won't change unless really necessary. It also means that the code still contains bugs, might not be as performant as you wish and documentation is not complete. After maybe three beta releases, which gradually improve stability and performance, we'd publish a release candidate which contains no known bugs anymore.

The FLOW3 team is aware of several open tasks, but what I'd love to know now is your assessment – what's missing? Please answer in the related thread in our mailing list, in the comments of this post or – if you spotted a bug – just file it in our issue tracker.

Leave a reply