We are working on release 1.0 and we are close. Since we are in the freeze mode of the RC1 function, the API will not change anymore, this is what we wrote about the stability of the API, and then:
Now that we are in freeze mode and the header for version 1.0, the outdated code and applications will start a lot more worried. We will not be the kind of framework where everything is interrupted every time the number changes. For example, v1.0.x will be backward compatible, but v1.1 may have some minor changes, which most likely will simply find and replace the application folder. v2.0? Well, that will be a different story.
Most of the errors that we know about have been fixed, and there is still a small list of errors left to fix, with which our small but active community helped us a lot. One of the main hurdles is writing unit tests for all parts of the Core and packages.
I myself am already developing production software on it, although for the summer release, and Dan Horrigan (our project manager) switched his employer to Fuel for their production.
source share