Sounds good. I think 12 month are more than enough to update code against a new APIs. For things that aren't widely used or are fairly easy to fix or just requires you to change some build scripts (or whatever) 6 month should be enough along with a deprecation warning on the console.
For browser support we don't need deprecation though because removing a permutation shouldn't do any harm unless developers/companies using GWT still want to support that permutation for their customers. In that case I think we should always do a major version bump whenever browser support changes, e.g. GWT 3.0 will not have IE6, 7, 8 and GWT 4.0 will not have IE 9 support. Then developers/companies can upgrade to the new major GWT version when they think its the right time regarding their own customers. It would also provide a clean mapping between GWT major versions and their browser support. -- J. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
