If we don't include com.google.gwt.experimental in the release, wouldn't we still break dependencies from gwt-user to the experimental stuff? If we need to modify an existing class with a reference experimental class, we either need to ship the experimental class or we need to create a branch.
I'd rather use bikeshed to keep the new stuff separate, and make sure that we don't have any dependencies on existing classes. We can override package protected methods by using a parallel package structure under bikeshed. Otherwise, experimental could create dependencies that are hard to catch. http://gwt-code-reviews.appspot.com/1060801/show -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
