Getting specific feedback directly from developers about their experiences with the platform is super important to us. It’s a critical part of how we optimize for real world performance and real world code patterns. This post is about the changes we’re making to our feedback programs in support of broadening and strengthening that feedback loop.
Your feedback about how we managed developer feedback over the last several releases guided the changes we’re making with IE9.
One of our commitments is to look at every single piece of feedback that we receive. The sheer volume of feedback from IE7 drove much of the design of the IE8 Beta Feedback process. For IE8, we limited the number of people who could file bugs and put no limits on who could vote on bugs. Many of the comments on that process were clear. At the same time, history has shown that users will often submit un-actionable feedback (registration required), large volumes of which significantly reduce our ability to react to high quality feedback (registration required). Some developers asked that we change the tool we use to accept bugs, noting things like the fact that the status and resolution information communicated isn’t always helpful. Below you can see some of the changes we made as a result of this feedback. The specifics of our programs and tools are at the bottom of this blog.
Here are the areas where we’re improving:
You’ll see some of these improvements with the Platform Preview released today. Other improvements will appear with future Platform Preview releases and the IE9 Beta.
At this stage, with the release of the Internet Explorer Platform Preview, we’re looking for developer feedback on the changes we’re making to the IE platform. As we discuss in the blog post About the Platform Preview, the Platform Preview is a light-weight frame around the IE platform while it’s under construction. It shouldn’t be used for compatibility testing.
Instead, we’d like developers to look at their sites with the Platform Preview and let us know if they have feedback or see issues in the platform. We’re looking for feedback in these areas:
In hearing your answers to these questions, we can validate the quality of the features, as well as ensure the additional functionality we deliver meets the quality standards you expect.
We have several tools and channels available to you when you find an issue or have a question. These channels will be available from now through the Beta:
If you’ve found an issue you want to report, we ask that you do the following:
We think this will help the discussion we all want to have work better.
Thanks again for all your feedback – we look forward to working with you to make Internet Explorer better!
Justin Saint Clair Program Manager
Update 3/16/10 5:40pm - Typo correction and updating bug links to indicate the registration is required to view them.