This is about all I needed to hear, although I do think it might turn into the CFML Advisory board debacle. This would just mean that Adobe brings it back in-house I guess:
Adobe will also have a team of Flex SDK engineers contributing to those new Apache projects as their full-time responsibility.
FINALLY, the statement that they don't hate Flex right now, just that it is a stopgap until HTML5 gets cool:
[W]e are incredibly proud of what we’ve achieved with Flex and know that it will continue to provide significant value for many years to come. We expect active and on-going contributions from the Apache community. To be clear, Adobe plans on steadily contributing to the projects and we are working with the Flex community to make them contributors as well.
Ok, I think this could work, but again, inklings of the last committee stuff they tried before:
We expect project management to include both Adobe engineers as well as key community leaders.
Adobe will continue to support applications built with Flex, as well as all future versions of the SDK
I don't buy this one. The first time there is a divergence in the committee, this will spell trouble for this initiative:
Adobe will undertake the required work to ensure Flash Builder is compatible with future releases of Flex SDK.
Well, while I still continue to learn HTML5 (the not-even-a-spec-or-supported-by-my-browser language), I will still happily create Flex applications for mobile. The complete post can be seen here, just scroll down past the stuff you read last time.