Anything I can do with https://codereview.appspot.com/6132056/ to help get it ready to go out with whatever release is deemed appropriate?
On 13 January 2013 18:24, Patrick Tucker <tucker...@gmail.com> wrote: > Any chance these can get committed? > > http://gwt-code-reviews.appspot.com/1876803/ > http://gwt-code-reviews.appspot.com/1762803/ > http://gwt-code-reviews.appspot.com/1833803/ > http://gwt-code-reviews.appspot.com/1785803/ > http://gwt-code-reviews.appspot.com/1736804/ > > On Saturday, January 12, 2013 11:02:41 AM UTC-5, Daniel Kurka wrote: > >> Repost from gwt-steering: >> >> Hi Everyone, >> >> a quick status update. In the last week a lot of patches have been >> contributed and some have already been submitted. >> >> At the beginning of next week I want to close of for any new patches, so >> that we can finish the work we are started. >> We are aiming for a code freeze at the 24th of Januar and a release a >> short time after that. >> >> So once again, if you feel strongly that you need to have something >> included in GWT 2.5.1 now is the time to act. >> We also have a couple of open issues that we would like to see in GWT >> 2.5.1, but might not make it (see: https://docs.google.com/** >> spreadsheet/ccc?key=**0AuK8EZ6jAAQrdDk1ME1lcmtWOWt3M**ngxOUlTMGJSVEE<https://docs.google.com/spreadsheet/ccc?key=0AuK8EZ6jAAQrdDk1ME1lcmtWOWt3MngxOUlTMGJSVEE> >> ). >> Feel free to to contribute patches and do code reviews on the issues >> listed in the document. >> >> -Daniel >> >> On Saturday, January 12, 2013 4:17:29 PM UTC+1, Thomas Broyer wrote: >>> >>> >>> >>> On Saturday, January 12, 2013 3:40:42 PM UTC+1, Julien Dramaix wrote: >>>> >>>> It would be nice to adapt the following paragraph [1] to explain the >>>> procedure for submitting code in gerrit. This paragraph is >>>> still mentioning svn >>>> >>>> >>>> [1] : https://developers.google.com/**web-toolkit/makinggwtbetter?#** >>>> submittingpatches<https://developers.google.com/web-toolkit/makinggwtbetter?#submittingpatches> >>>> >>> >>> I think the idea was to wait until the move to Git is complete. For now >>> the Git repo is still a mirror of the SVN repo (git-svn) which is a mirror >>> of Google's internal Perforce. >>> To complete the move, we'll rewrite the history to remove all big files >>> (prebuilt plugins and api-checker reference jars) so all contributors will >>> have to re-sync their Git repo. >>> So in the mean time, SVN and Rietveld is still OK, though "deprecated". >>> >>>> -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
