I kind of agree not calling it GWT 3.0. I would not name it completely different, maybe something along the lines of GWT X1, GWT RST (abbr. of reset) or GWT Next. I am pretty sure we could come up with something more distinct to indicate that this release is a lot different and a reboot of GWT.
I also think that without drop-in replacements for widget code, UiBinder and GWT-RPC a lot of apps will not migrate to the new GWT because it is simply not cost effective. The GWT surveys shows that the majority of apps depend on these features. Maybe with the help of Singular it is possible to incrementally rewrite your UI until its compatible with GWT 3.0 but you still need to rewrite a lot. I think at the end it boils down to if you want to use the new compiler or if you are fine with the current SDM development speed of the 2.8 release. Because all the rest of GWT 3.0 can also be used with GWT 2.8. -- J. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/76cb0c63-a981-4b54-95bf-ebbd8f773311%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
