On Tue, Sep 4, 2012 at 11:53 PM, Ray Cromwell cromwell...@google.com wrote:
Thomas, thanks for all of the work on this, but we will have to delay
this until after we get the open-source git/gerrit repo up and
running.
No problem (no, really!)
Someone had to do it and I was in the mood for it;
Thomas, thanks for all of the work on this, but we will have to delay
this until after we get the open-source git/gerrit repo up and
running. A preliminary investigation of internal Google apps shows a
bunch of them still relying on EventListener, so we'll have to create
an uber-patch to fix all
give internal teams a lead time to fix their usages first
Haven't these been deprecated since ~2008? How much more lead time is
necessary? Is there a @NoSeriouslyWeReallyMeanItDeprecated annotation
we should use instead?
Even with the new process, if google-vendor is going to diverge from
On Tue, Sep 4, 2012 at 6:48 PM, Stephen Haberman
step...@exigencecorp.comwrote:
give internal teams a lead time to fix their usages first
Haven't these been deprecated since ~2008? How much more lead time is
necessary? Is there a @NoSeriouslyWeReallyMeanItDeprecated annotation
we should
In ordinary cases where there is no API change, I don't think the
problem is so severe. But removing APIs, even deprecated ones, is
always hard, just look at the Web and the debates over vendor
prefixes. At Google we do have tools that help with 'company wide
refactoring', the EventListener issue
Awesome work, Thomas!
- Stephen
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
