We are excited to tell you about two changes to GWT today based on your feedback in the GWT developer forum.

First, we've transitioned to using a real issue tracking system on Google Code so that you can report issues and workarounds directly to our issues database rather than just talking about them in the forum. This has been one of the most requested features in the forum, and we hope it will help make our development process more transparent.

Along with the new issue tracker, we are changing the way we release new versions of GWT. We're going to release at least one "Release Candidate" build of each new version of GWT before we release the official version. This will let the GWT team release versions for testing more quickly, and will make it clearer when it's "safe" to upgrade your production-quality projects to new, official versions.

As part of our effort to become more transparent, we have labeled all of the features and bugs that we are working on for our next release, GWT 1.2 Release Candidate, in the issue tracker. Just search for [milestone:1_2_RC] in the issues database to see the complete list. (And yes, Mac OS X hosted mode support is on the list.)

Please let us know what you think in the developer forum. We're excited to make GWT development more interactive, and we really appreciate all of the candid feedback we have gotten on our development process to date -- keep it coming!