Thanks for your follow-up. I didn't take it as criticism and hope I didn't come off as defensive. I only meant to point out that GWT really does rely heavily on the open source community and we neither desire nor are able to do everything ourselves. The GWT team is really thankful for the contributions of the open source community around maven and GIN. Community support for these allows us to focus our limited resources on improving the compiler, adding new features, widgets, etc.
I completely agree that we could do a better job of communicating our roadmap and schedule to facilitate planning by all parties; however, these are often quite fluid and in many cases involve things we can't yet share publicly like last year's acquisition of Instantiations and the resulting addition of GWT Designer to GPE. So... point taken, but don't hold your breath :-) Fortunately, as Thomas points out, GIN and gwt-maven-plugin are largely independent of GWT releases. gwt-maven-plugin intentionally decoupled in version 2.1.0 IIRC, and GIN is independent as long as we maintain backward compatibility (we're really sorry about the GIN breakage in 2.2.0). Even then, the GIN community worked with the GWT team to get it resolved in a matter of days. Best I can recommend is to be involved in the open source projects where release cycles matter the most to you.
Regards,
/dmc
On Wed, May 4, 2011 at 4:03 PM, David Chandler <drfibonacci@google.com> wrote:
They're open source projects. Someone == you.Google doesn't maintain 3 of the 4 projects; however, we generally post the beta announcements on the GWT blog a week or more in advance. If there's something more we can do to notify the other projects, I'm all ears.
/dmc--On Wed, May 4, 2011 at 3:00 PM, Blackberet <ramonjsantiago@gmail.com> wrote:
Someone should give some thought to doing release trains of gwt,
guice, gin, and the gwt maven plugin.
This is really important for those of use who are in organizations
where our projects must be built via maven.
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
David Chandler
Developer Programs Engineer, Google Web Toolkit
w: http://code.google.com/
b: http://googlewebtoolkit.blogspot.com/
t: @googledevtools
--
David Chandler
Developer Programs Engineer, Google Web Toolkit
w: http://code.google.com/
b: http://googlewebtoolkit.blogspot.com/
t: @googledevtools
On Wed, May 4, 2011 at 9:25 PM, Blackberet <ramonjsantiago@gmail.com> wrote:
Please don't mistake a suggestion for improvement by a consumer of
your technology as a criticism.
I feel fairly confident that a significant percentage of users that
consume GWT also consume the other three pieces of this stack as well.
I understand that Guice can be consumed separately without the
slightest dependence on GWT.
The other two pieces of this stack, GIN and the GWT Maven plugin have,
in the past, caused compatibility problems, if not outright failures
in builds. I understand that the GWT releases come first, and that the
others are not your concern. It would facilitate my planning, and that
of other developers, if you and the owners of the other three projects
were to schedule release trains periodically. We could then plan for
technology stack updates as part of our development lifecycle.
On May 4, 4:03 pm, David Chandler <drfibona...@google.com> wrote:
> They're open source projects. Someone == you.
>
> Google doesn't maintain 3 of the 4 projects; however, we generally post the
> beta announcements on the GWT blog a week or more in advance. If there's
> something more we can do to notify the other projects, I'm all ears.
>
> /dmc
>
>
>
>
>
> On Wed, May 4, 2011 at 3:00 PM, Blackberet <ramonjsanti...@gmail.com> wrote:> t: @googledevtools- Hide quoted text -
> > Someone should give some thought to doing release trains of gwt,
> > guice, gin, and the gwt maven plugin.
> > This is really important for those of use who are in organizations
> > where our projects must be built via maven.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google Web Toolkit" group.
> > To post to this group, send email to google-web-toolkit@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-web-toolkit+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/google-web-toolkit?hl=en.
>
> --
> David Chandler
> Developer Programs Engineer, Google Web Toolkit
> w:http://code.google.com/
> b:http://googlewebtoolkit.blogspot.com/
>
> - Show quoted text -
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
--
David Chandler
Developer Programs Engineer, Google Web Toolkit
w: http://code.google.com/
b: http://googlewebtoolkit.blogspot.com/
t: @googledevtools
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment