Maybe you guys could take a look at this one too?
http://code.google.com/p/google-web-toolkit/issues/detail?id=5424

On Thursday, March 8, 2012 9:22:11 PM UTC-5, Ray Cromwell wrote:

> Greetings Contributors,
>
> First an apology, I realize many of you have put a lot of work into
> contributing to GWT, and we haven't exactly been speedy in picking
> these up. There's been turnover and reorgs, and some of the original
> code reviewers have left the team, or even left Google, and so some of
> the patches you've contributed have been forgotten, or are in limbo.
>
> With GWT 2.5 coming up, now's a chance to rectify this. If you have
> had codereviews sitting dormant, or worse, approved and finished
> patches, reply to this thread with links. We will start collecting
> them and landing them in GWT for the upcoming release. Dust off those
> patches sitting in the issue tracker too.
>
> Going forward, we are investigating ways to avoid this problem such as
> enabling outside contributors direct commit access in the future. (We
> recognize GWT's progress has often been blocked by Google itself as
> the gating factor, and as a true open source project, that shouldn't
> really be the case. There are obvious concerns with things like
> security, since many of Google's own services use GWT)
>
> -Ray
>

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Reply via email to