As part of the 2.0 postmortem, we discussed the importance of cleaning up the issue tracker in order to have a better view of high priority issues that need to be resolved in upcoming releases. You may have already seen action being taken as we have started reviewing, assigning, and requesting more information for more recent (or long standing) issues.
Another step we will be taking is to trim the overall list by closing all issues, opened prior to 01/09, that are still marked as status "new". We're assuming (and in some cases this will be incorrect) that these older issues have either been fixed, or a suitable workaround has been found. That said, if you believe that it's still an issue (even after upgrading to 1.7.1 or 2.0), we urge you to reopen it and update the comments accordingly. Our belief is that this process will help us tighten up our focus on critical issues, as well as issues where patches have been submitted. Thanks, Chris -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
