According to https://groups.google.com/d/msg/google-web-toolkit-contributors/ay4gLCa9cuM/w8fNyLS6xKgJ, work on master and then cherrypick to release/2.6 (IOW, the release branch will never be merged back to master)
On Thursday, November 7, 2013 7:09:58 PM UTC+1, Cristiano wrote: > > Hi all, > I'm making a patch for the issue > https://code.google.com/p/google-web-toolkit/issues/detail?id=8424 > > Actually I have tested the patch over the branch "release/2.6" => > > $ git status > # On branch release/2.6 > # Changes to be committed: > # (use "git reset HEAD <file>..." to unstage) > # > # modified: servlet/build.xml > # new file: servlet/gwt-servlet.bnd > # > # Untracked files: > # (use "git add <file>..." to include in what will be committed) > # > # build/ > > is this correct or should I work on the "master" branch? > > thank you! > Cristiano > -- 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.
