OK, will do, thanks. On Dec 21, 10:41 am, Chris Ramsdale <[email protected]> wrote: > 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 recent (and long > standing) issues. > > Another step we will be taking is to trim the overall list by marking > issues with a status "new", that were opened prior to 01/09, as > "obsolete". 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
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
