As a ~24h later status report, we assembled a list of 26 changes that were outstanding, and started working on manually importing them individually so we could parallelize our efforts. It's basically all we've worked on today so far.
Current status is: - 12 of them have already been merged. - 3 of them add new JRE 7 dependencies to unit tests, which breaks since we currently still need to support JRE 6 internally. (We're still discussing what to do about these, but they don't seem like a problem.) - 1 of them broke gwt-exporter <https://code.google.com/p/gwt-exporter/>due to the latter depending on GWT internals; fix is in review - 2 more cause performance regressions or breakage that rluble is investigating - 4 more are currently in review/testing - 4 more are still pending review So we're about half to two-thirds caught up now, and progressing quickly. I'm hopefully optimistic that we can re-enable CR+2 tomorrow or early next week, and start accepting patches again. On Wed, Jun 19, 2013 at 12:45 PM, Matthew Dempsky <[email protected]>wrote: > Hi GWT contributors, > > We're happy to see so much increased activity in the recent weeks since > opening Gerrit to direct external contributions! Unfortunately, the new > velocity has stressed our workflow for importing changes back internally > within Google, and we've now fallen a couple weeks behind master. > > After discussing this some, we've decided we need to *temporarily*disable > CR+2 on Gerrit while we catch up internally and experiment with a > new more scalable workflow for going forward. As soon as we're caught up, > we'll reallow CR+2 and try to ramp up again. > > We really regret the inconvenience in the meantime! :( > > Thanks, > Matthew, on behalf of Google's GWT team > -- 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.
