On Sunday, September 1, 2013 1:56:55 AM UTC+2, Matthew Dempsky wrote: > > I think having an official deprecation policy like Guava's is a good idea, > and I'd support going with Guava's to start with. > > There is the issue though that Guava is purely a Java library (?) so it > can uniformly deprecate things via the @Deprecated annotation, whereas GWT > has many non-Java things we might want to deprecate (command-line flags and > browser support come to mind) so we need an official way to deprecate those > features/functions too. I think just mentioning them in the release notes > is a good way to mark them officially deprecated (but we should also try to > warn users more directly when possible). > > Lastly, we should decide if we want to grandfather in some existing things > as deprecated, or whether they should all go through the same deprecation > process. E.g., I think Visibility.LegacyPublic is reasonably considered > deprecated since its Javadoc discourages use, but it's not actually marked > @Deprecated. And I use this just as an example; I think it's safe to kill > now, but if there's any concerns about setting a bad precedent for other > removals, then I'd support just marking it @Deprecated for now instead and > waiting a few releases before removing it. >
DeRPC isn't @Deprecated either ;-) so yes, we should grandfather in a few things. (LegacyDeploy was about deprecating -extra in favor of -deploy for a few things so I think it's safe removing it –unless some big users like Sencha, RedHat or Vaadin would prefer we first deprecate it; but it should be safe no longer using it in GWT proper– and DeRPC never exited the "experimental" stage, we should have deprecated it when we started discouraging its use on the dev guide; they're probably the only 2 things here) -- 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.
