A quick preface to this entries core message about getting involved to help improve the quality of the next releases of the Adobe Flash Player 10.1 and AIR 2.0:
Adobe’s Flash Player has been getting a lot of press lately. Mainly in regards to HTML5, the Apple iPad (and its closed garden), performance on the Mac OS X platform, the changing face of mobile and other related discussions. The crux being Flash’s relevance and importance now and in the future. Posts and comments around the web have covered the entire spectrum, with everything from loquacious pontificating, to lugubriously laconic, to outrageously uninformed. They have all been quite polarizing in one direction or another. The biggest take away for me after absorbing everything for a week or two, has been the fact that the right people are listening and hear us and are also speaking up or acting. There have been several posts that I felt were especially well said and or align well with my own personal thoughts, so I wanted to highlight a few of them:
- Kevin Lynch, Adobe CTO: Open Access to Content and Applications 
- Follow up comments from Kevin  on that posting.
- John Nack, Adobe Photoshop Product Manager: Sympathy for the Devil  and Adobe Isn’t in the Flash Business 
- Grant Skinner: My Thoughts on the Future of Flash 
- Jeremy Allaire, CEO of Brightcove: The Future of Web Content – HTML5, Flash and Mobile Apps 
- Mike Chambers, Principal Developer Relations Adobe: Some personal thoughts on Apple and the trend towards closed platforms  
There are quite a number of other great posts around, and even more that I felt were just way off base or totally wrong – but for me again the biggest take away is that people are listening and acknowledging things that can be improved and putting their money where their mouth is and committing to certain actions and more transparency. Kevin’s promise to have the Flash Player teams publish some performance metrics for the various platforms, the transparency and insight that Emmy Huang Flash Player Product Manager blogged about  and some plans to improve bug reporting process’s around the Flash Player – these are really great things that exemplify the level of commitment and care that Adobe places on its products and the community of developers and designers that use them.
So how can you get involved to improve things and shape the future and stability of Flash Player 10.1 and AIR 2.0? Get involved and install the latest betas and test them!
Then test against your existing content and applications, surf the web and check out existing content and most important of all: Report any bugs or problems you find at http://bugs.adobe.com/  – This is the critical step as engineering teams use bug reports to reproduce errors, and improve the overall quality and stability of the releases. You can also browse through existing bugs and ECR’s (requests for enhancements/new features) and vote for ones you determine to be important.
Flash Player 10.1 and AIR 2.0 are both at public beta 2 and available through http://labs.adobe.com/ with beta 3 releases a few weeks away and final candidates expected within 60 days. Now is the time to get involved and test and report any issues bugs you find.
Ted Patrick  has a great post summarizing this effort, and another way you can help is to spread the word by tweeting directly about this: Improve Flash 10.1 & AIR 2.0 via Beta 2 http://bit.ly/cty7Nm READ & RT #Flash #AIR #QUALITY
Finally, its also worth noting that you can sign up to be considered for Adobe’s Prerelease teams to get further involved in beta testing their products via this link: http://labs.adobe.com/wiki/index.php/Prerelease