Hi Daniel, Thanks for taking the time to respond. I watched your IO video. Great job btw, and congrats on your new position at Google. I completely understand the need to clean out the issue tracker. It has certainly been neglected over the years. My primary concern over all else is for Accepted issues in general. Presumably these were issues that other Google engineers felt were important enough to mark for inclusion into GWT.
I understand now that GWT has the Steering Committee guiding it, certain priorities may have changed. That's fine, I accept that! However, as GWT continues to evolve, three questions come to mind: 1) Other than age, is there any other criteria for marking an Accepted/Planned issue as stale? 2) Moving forward, can we assume that any *newly* Accepted issues will be tackled in a reasonable time frame (i.e. not still floating around in 2016)? 3) How much weight does the Steering Committee give to heavily starred issues (i.e. the kind that are too large for individuals to tackle)? The top three open issues are: java.util.Calendar emulation<http://code.google.com/p/google-web-toolkit/issues/detail?id=603>(483 stars) WebSockets for RequestFactory<http://code.google.com/p/google-web-toolkit/issues/detail?id=267>(218 stars) GWT-compatible Protocol Buffer Compiler<http://code.google.com/p/google-web-toolkit/issues/detail?id=2649>(164 stars) <-- start with this one! Again, thanks for taking the time to respond. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
