News of the change of leadership came at Google I/O from Ray Cromwell, the Google technical lead for GTT.
Cromwell, who will serve as the committee chairperson in the first instance, explained that with a committee controlling the future road map of GWT:
It will no longer be Google as dictator.... We have to be responsive, and we have to think more about what other people [support]," in GWT,
The other companies represented on the committee include Vaadin, Sencha, and Red Hat, and members include GWT advocates Thomas Broyer, Christian Goudreau, and Daniel Kurka.
According to Cromwell, the committee has already had a couple of meetings and has decided to move the GWT repository from Subversion to Git. GWT has also forked two official branches: a master dev line trunk, for testing out bleeding-edge capabilities, and a beta branch, which will hold new capabilities selectively taken from the dev line trunk branch.
The timeline presented at Google I/O shows that GWT 1.0 was released in 2006, had its first open source release in 2007 and reached version 2.0 in 2009 when it added major new features including DevMode, DraftCompile, UI Binder, LayoutPanel. CodeSplitter, ClientBundle, and CssResource. Versions 2.1 and 2.2 both had major features, with RequestFactory and Editor Framework in the former in 2010 and GWT Designer and HTML5 support in 2011. A few months later, Version 2.3 extended HTML5 support and improved AppEngine integration. Version 2.4 also in 2011 had Maven and RequestFactory enhancement.
The upgrade also includes Elemental, an experimental library providing lightweight, to-the-metal Web programming, primarily targeted at mobile development.
Other features include:
New Compiler Optimizations
Closure Compiler Integration
Code Splitter improvements
Better Stack Traces with SourceMaps
UiBinder and CellWidget updates
A final version of GWT 2.5 is expected in less than a month.
As we reported yesterday, Google has closed more of its redundant and unwanted projects and while GWT doesn't fit into either category putting it in the hands of a steering committee does seem a bit like sweeping it to one side.
On the other hand, having Google loosen it hold on the project may be just what is required for it to flourish.