I see the problem here: I don't consider GWT just a web framework (and maybe I'm wrong about that). I consider it a platform on which web frameworks are built (like Vaadin, GXT, Errai and so on). It involves compiler, language, tooling *and* a web framework. And assuming it as a platform, I tend to compare it with other important stuff to my dev daily work, such as my OS (Ubuntu, next major release on 17-Apr<https://wiki.ubuntu.com/TrustyTahr/ReleaseSchedule>) , my browser (Firefox, next major release on the week of 04-Feb<https://wiki.mozilla.org/Releases#Firefox_27>) , my most used IDE (Eclipse, next major release on 25-Jun<http://wiki.eclipse.org/Luna/Simultaneous_Release_Plan>) and my most used programming language (Java, next major release on 18-Mar<http://openjdk.java.net/projects/jdk8/milestones> ).
If I would build a commercial web framework on top of GWT, I'd like to have a concrete idea of the development cycle to be ready to upgrade my framework on time for my customers. As a GWT developer as I am now, and looking at it as a platform - not just a web framework - I really miss a page where I can find the details about the release, with steps and expected dates for each step to conclude, in a structured and reliable way. Things can go wrong and dates can be changed (as in any project), but it should be the exception, not the rule. Anyway, it's just about how I feel about the project, and, as I wrote, I can be wrong. On Monday, January 6, 2014 3:09:17 PM UTC-2, Jens wrote: > > 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
