Most of us on the Flex team come from the world of desktop software, which has a certain rhythm. You plan, you prioritize, you build it, you test it, and you ship it. During this cycle, each turn of the crank takes 12-18 months.
The Flex project is similar and it’s not. On the one hand, the Flex product is like desktop software in that we probably do want to keep it stable for a while before releasing new functionality. When people are depending on your framework, it, you shouldn’t change it every month.
On the flip side, the Flex team has a responsibility to “keep things going” on a steady basis. In that way, it’s very different from desktop software. To keep the Photoshop community going, the best thing to do is to ask the engineering team to put their heads down and to keep working on the next killer version of Photoshop. To keep the Flex community going, you want the team to be more actively engaged throughout the process. Most of the dev team is active on lists like flexcoders. People like Ely do experiments with Flex and post about them.
One of the most important pieces of the puzzle is documentation. We are trying to find new ways to move faster on getting documentation to customers, and as part of this, the doc team is now posting new chapters to the Flex documentation as soon as they have written them.
There are other “ecosystem” plans that we haven’t put into action yet (shhhhh!). In the meantime, what do you think the Flex should be doing? What would help you? What would help the Flex community in general?