Go语言的版本控制系统将从Mercurial切换到Git，而Go项目也将托管在GitHub上，并将使用谷歌托管的Gerrit作为代码评审。Google表示迁移将在12月初发布Go 1.4之后启动，Go 1.5的开发将全部在 GitHub上进行， Mercurial 树将在1.4发布之后关闭。国内Go爱好者有福，再也不需要翻墙了。 [Rob Pike golang-dev 发布的消息](https://groups.google.com/forum/#!topic/golang-dev/sckirqOWepg)： Go contributors, When Go became an open source project 5 years ago, Mercurial was the best choice for us for a number of reasons, most important being the ability to support our choice of code review system. Mercurial has served us well, but it's time to move on. The world today is quite different from the world then. Most members of the Go community use Git and host their work on GitHub, and we should join them. Thanks to the efforts of open source projects like Android, we now have access to a Git-based code review system that fits our workflow. We are therefore pleased to announce that we plan to migrate the Go project and its subrepositories to GitHub. The issue tracker and the wiki will also be moved; all data will be preserved. We will use a Google-hosted instance of Gerrit for code reviews. The transition will happen soon after the 1.4 release in early December. All development for 1.5 will happen in GitHub; the Mercurial tree will be closed to changes after the 1.4 release. We are still developing the plan and will explain more about the transition in the coming weeks. There is one thing we need to do beforehand, which is to gather the permissions necessary to migrate the issues on the issue tracker. If you have added issues or comments to the Go issue tracker, please visit go-issue-migrator.appspot.com and click on the "Yes, let's do this" button and authorize our migrator application on GitHub. This gives us access to your GitHub account to enable us to re-create your issues and comments as you, so that you will be notified of changes to issues you've contributed to. (It's OK to not give us this permission; if you don't, your issues and comments will be owned by a "gopherbot" account but will still be attributed to you.) We only need your credentials for the transition; once it's done we'll throw them away and—to be sure—you may revoke the token yourself. As always, our thanks to the community for all the work you do to make Go succeed. Rob P.S. For those keeping score, this will be Go version control system number four. Go development started in Subversion, moved to Perforce, then Mercurial, and soon to Git.