This article is from my translation on infoq Chinese siteArticle, Original address is: http://www.infoq.com/cn/news/2012/05/eclipse-gerrit
Recently, the eclipse Foundation has released a much-anticipated Gerrit for Git-basedCodeReview and patch submission. Gerrit is a web-based tool used to receive git commits. infoq has previously reported on it. The audit tool is located at https://git.eclipse.org/r /.
Gerrit is widely used in many open-source projects, such.
Chris aniszcsyk has been supporting git and Gerrit for a long time. He said:
Several of our contributors have been promoting Gerrit development over the past few years to improve the eclipse infrastructure. Now I'm glad to see that all these dreams come true. We were very satisfied with the use of Gerrit in the egit and jgit projects for a long time. Now, the eclipse submitter has a convenient way to use git for code review (if they want to add this process to the Project ).
However, the eclipse process still needs to catch up with technical improvements. Git, which is widely used as a DVCs, is not very important for those who branch eclipse on GitHub. It provides improvements to this function, you can directly submit it to the repository. However, this process is mainly to add "patches" to Bugzilla, which is usually not very common (but not impossible) in the DVCs world ).
But Gerrit provides users with an agreement that users need to agree to before their first login, which is usually used to accept the license agreement, the eclipse process said:
Contributors maintain bugs or comments in Gerrit to indicate that they will:
- 100% authorization for the content contributed by the Service
- Have the right to contribute content to EPL
- Contribution under EPL
Currently, we require contributors to be able to clearly abide by the terms of use when creating an account; we further require contributors to adhere to the above three issues for each contribution. Consent can be provided in the bugzilla record (if any) or in the comments connected to Gerrit push.
An ongoing discussion shows that this rule is often ignored in other version control systems in the past.
With the release of eclipse 3.7.2, many projects are still using CVS or SVN repository because it "prevents" 3.7 of stream building, it seems that there will be a huge gap between git and eclipsecon 2012. There are still 310 days before the end of CVs, and many projects will be rolled out of CVs or even SVN. If the problem of the eclipse contribution protocol can be solved, and the Gerrit patch can be integrated into the IP workflow, we will see more contributions flowing into the core platform library.
View Original English text:Gerrit at the eclipse Foundation