Adobe engineering is headed into the final stretch of development of Flash Player 10.1 and AIR 2.0. We need community help to identify quality issues with your deployed and in-development content. While both Flash and AIR are tested extensively internally, every beta we receive valuable feedback from the Flash community and beyond.

Here is how you can get involved:

1. Download and install Flash Player 10.1 Beta 2 and AIR 2.0 Beta 2
2. Test the new beta runtimes with your content and applications.
3. Log bugs at bugs.adobe.com. Engineering teams use your bug reports to reproduce errors and improve the runtime quality.

As far as beta timelines, beta 3 releases are a few weeks away and release candidates are expected within 60 days. Your involvement and assistance during this critical development window are really important and will only improve Flash Player and AIR quality.

Please also help spread the word about the beta process via Twitter:
Improve Flash 10.1 & AIR 2.0 via Beta 2 http://bit.ly/aN4Qk0 READ & RT #Flash #AIR #QUALITY

Although some people may/will disagree, Adobe does listen to feedback from the community. ;-) Obviously there’s only so much you can add in one release cycle and therefore it could be that your favorite feature didn’t make in a particular release.

There is an easy way to influence which features will be considered for Flash Player, Flash Builder/Flex SDK, Blaze DS and the ActionScript Compiler. Adobe actively requests that developers log bugs and feature requests using JIRA, which is hosted at bugs.adobe.com. The product teams review all the feature enhancements that are logged and pay particular attention to those requests that have community support, by way of the number of votes received. In other words: Make yourself heard! Remember the “Make Some Noise” campaign that Andre Michelle started to get raw audio APIs in Flash Player? The whole Flash community was talking about it… and Flash Player got the audio APIs.

To summarize: Make sure you add your feature/enhancement request to the open bug base and make sure you get lots of support. This is obviously not a guarantee that it will be added to the next release of a product but I can guarantee you that we do take the feedback you give us very seriously and that all feedback is used to shape the future of the Flash Platform.

If you haven’t used bugs.adobe.com before, you can find a quick guide to getting started here.

Doug Winnie, Adobe’s Group Product Manager for Workflow, is seeking your input. Doug is responsible for maximizing workflow collaboration between Adobe products, platforms and technologies and is currently investigating what role Fireworks plays in people’s workflow.

So… How does Fireworks fit in your workflow? Leave a comment on Doug’s blog.