Hi, I also had hoped we would be a lot further along in the process by now. There's a variety of reasons for this, but it's just mostly it's that things just have taken a lot longer than everyone originally expected. We are still trying to sort out the JIRA infrastructure (there been work on this and last I heard they were about to do a test import again), the full Mustalla test suite (Adobe have donated the checkin tests and tests for button) and working the parity 4.6 SDK release (which need to abide by certain fairly restrictive conditions to what can/cant be packaged in it). While I couldn't predict when those 3 things will be complete significant progress have been made on all of them.
Adobe does have full time resources (Alex and Carol) working on further donations and getting the first parity release out the door and others are helping where they can/as required. Once these 3 items are complete (JIRA, testing framework, initial parity release) we'll likely to see a lot more activity from current committers and Flex SDK users and then Adobe resources can work on donation of other parts of Flex SDK that are yet to be donated (like automation, new spark components, new compiler etc). I have quite a few things I would like to work on (time permitting) but without JIRA and a full testing framework it's difficult to be able to commit patches and new code to the SDK. > - We are attached to an application that could die at anytime as have > already happened Flash Catalyst, Flash Player Debugger for Linux and > others. The Flex SDK is not a product as such so can't suffer the same fate as say Catalyst. The Flash Player is still being supported by Adobe and is part of Adobe's future plans. I assume you've seen the FlashPlayer roadmap for the next several versions of the Flash Player? http://www.adobe.com/devnet/flashplatform/whitepapers/roadmap.html > - there is a really fast movement from people that loved Flex to > technologies such as javascript + html5 + css3, including some core people > from Apache Flex. Some of the "core" people are exploring the use of other technologies but that is normal, being a programmer/developer mean continual learning and playing about with new technologies. I been using Javascript since way back in the IE3/Netscape days and I'll use it again but that doesn't mean I'm moving away from Flex. :-) > - some flex projects are becoming ghosts (no commits for quite some time) Any projects in particular? I know for instance FlexLib hasn't been getting a lot of love but that was the case well before Flex moved to Apache. as3 commons on the other hand is in active development. One way to try and fix this would be to try and get people from this list involved in contributing to those projects. > - blogs about flex are dying or moving to other technologies IMO Blogs tend to written about new "exciting" emerging technologies. Flex as a mature and proven technology doesn't attract the large audience that most bloggers want. Thanks, Justin
