At least on Google side we were assuming we will move to Github for issue tracking but I don't know if that came up in any steering committee discussions.
On Thu, Apr 23, 2015 at 12:41 PM, Jens <jens.nehlme...@gmail.com> wrote: > In 4 month code.google.com will be read only and as time can pass by fast > I think we might want to start discussing some alternatives. > > > Bug tracker: > > 1.) Install any reasonable bug tracking software on bugs.gwtproject.org. > That software should have a good API so we can migrate issues easily and > possibly integrate with Gerrit: assigned issue to next release version once > a review is submitted, mark issue as fixed once the review is merged and > reopen the issue if a git revert has been done. That would keep the bug > tracker more up-to-date without manual work. Although not really needed but > a nice side effect might be that the IDE can connect to the API to show > issues in the IDE and possibly assign them to you if you want to work on > some issues. > > 2.) Move issues to Github although I am not sure if that is possible if > you only have a mirror project on Github. If its not possible with just a > mirror, the hardcore solution would be to fully move to Github and use some > Gerrit/Github integration. A nice side effect would be that we could allow > pull requests which are then reviewed in Gerrit. > > > SVN tools project: > > Get rid of it for future builds. We could upload libs on bintray and use > ANT to download only the ones you need to build the current checkout of > gwt. Might be a bit clunky for now but if GWT switches to a build system > that understands maven repos we already have libs in place on bintray. If > doing so we would probably have https://bintray.com/gwtproject/libs. > In order to be able to build older GWT releases from source we still need > a backup of the current SVN tools repo. As it will be a read only backup it > is probably fine to just convert it to git and put it on googlesource.com > > > > What do you guys think? > > > -- J. > > > -- > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-web-toolkit-contributors/2d59da73-f0d3-4b84-bcc4-737c2f5c8e19%40googlegroups.com > <https://groups.google.com/d/msgid/google-web-toolkit-contributors/2d59da73-f0d3-4b84-bcc4-737c2f5c8e19%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA2YeQukQDuLYbd4g%3DcAMusje7WV8ExbSY_64OukmERvHw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
