> > That's how that strange conversations about GWT being dead or alive begin. > We need a concrete schedule. We need a concrete release plan. We need > something strong enough to trust - not informal conversations. >
Don't take me wrong but show me some web frameworks out there that have *concrete* schedules and release plans. They are all communicating their plans in a vague manner like "minor releases roughly every 9 month" (taken from Django as example. Haven't even found anything similar for jQuery). As far as I remember on Google IO 2013 Ray said that GWT tries to aim two releases per year (roughly around Google IO and november/december). So thats pretty much the same information you get from other frameworks. I think GWT lacks an official (announcement) blog or something similar on its homepage. If a date is announced on this blog then it should happen to this date. But as long as a release is planed/discussed in a contributors mailing list I wouldn't consider it an official release date. And even with such an (announcement) blog on the GWT homepage a release date can change. Prominent example of changed release schedule would be Java 8 which should have already been released. -- J. -- 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.
