We're working towards the 1.0 final release and we're close. As we've been in a feature freeze as of RC1 the API won't change anymore, this is what we wrote about API stability then:
Now that we are in a feature freeze
and heading to v1.0, legacy code and
applications will start to become much
more of a concern. We won't be the
sort of framework where everything
breaks every time the number changes.
For example, v1.0.x will be backwards
compatible but v1.1 may have some
minor changes - which most likely will
just be a find and replace across the
app folder. v2.0? Well that will be a
different story.
Most of the bugs we're aware of have been fixed and there's still a small list of bugs left to fix which our small but active community have been very helpfull with. One of the major hurdles left is writing Unit tests for all parts of the Core and the packages.
I am myself already developing production software on it, though that's slated for a summer release and Dan Horrigan (our project lead) has had his employer switch to Fuel for their production.