Today, we finished a migration of the codebase from Google Code's SVN repository to Git repository hosted on GitHub.
Git is a distributed version control system gaining popularity in many companies and open source projects. We've been using it for Review Board development for quite some time, pushing changes to SVN once they're ready for the release. We felt moving to it fully was a natural next step.
Moving to Git has many advantages. We can make changes public before they're ready for inclusion by putting them on development branches. Users can play with the branches, easily merge between them, and even contribute to changes that are in-progress. Companies can maintain forks of the Review Board codebase with their own customizations and still keep them in sync without nearly as much effort as with SVN.
Review Board Checkouts
The main Review Board project repositories are up on the Review Board GitHub account. RBTools and Review Board itself have their own repositories now.
To check out a repository locally, first install Git and then clone the repository. For example:
$ git clone git://github.com/reviewboard/reviewboard.git
This will create a reviewboard directory containing the codebase. To fetch new changes, make sure you're on the master branch and then pull the latest changes:
$ git checkout master
$ git pull origin master
From time to time, you'll find experimental branches on the GitHub forks ran by David Trowbridge and Christian Hammond.
Contributors who have supplied patches to Review Board that are still pending will need to move their patches over to Git. An e-mail will be sent out to all contributors with pending patches with some instructions on this.
If you're unfamiliar with Git, take a look at GitHub's guides on using Git and GitHub.
Our project's Review Board server has been updated with the new repositories, "Review Board" and "RBTools." There's also a new "RBTools" review group, for changes against RBTools.
If you have any questions or need help, please ask on the Review Board mailing list.