I think one issue is that Google builds their apps from GWT master branch. They don't need release versions. That also means that the master branch is stable and its fine to use it in production.
The company I work for does the same. We have some custom GWT patches and build or own GWT every one or two month based on the master branch. We don't really had any problems with that approach. Some days ago in IRC and proposed that GWT should do regular releases from the CI server that do not have "-SNAPSHOT" in their names and have a slightly different version number, e.g. <major for breaking changes>.<timestamp>. These CI releases could probably also be done after Google had tested the build against all their internal apps. That way a new release can be done every one or two month and the enterprise guys are happy because no "-SNAPSHOT" dependency is in their build file. Maybe that is an acceptable compromise between using SNAPSHOT builds vs. a released version. At least it would more closely match how Google works and Google is the main committer. Also some days ago Thomas Broyer said that they do a (roughly) monthly steering group meeting but sometimes they don't release meeting minutes because they contain confidential information (from one or more of the companies in the meeting group). I proposed to just remove such information because it is very likely not relevant to the community at all and then regularly release the meeting minutes. Maybe they pick up both points in the next steering group meeting. -- J. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
