|[jgit-dev] Jgit Gerrit Review Process: Some Questions|
Hi there!I am a computer scientist at Technical University of Munich. My field of research is Code Reviews. My research questions focus around which types of defects are usually found during code reviews in open source projects. For this, I want to set-up an empirical study with open source systems employing Gerrit Code Reviews. Jgit could be one of them.
A quick scan through the code base of Jgit suggested to me that code reviews are mandatory for every commit. Before I could include Egit into the study I have a few questions:
1) Is this ture, i.e. is the review policy rigorous? Or are there changes to the repository that can go un-reviewed?
2) Since when do you use code review?3) I noticed there can arise changes without a linked bugzilla id. When/why does this happen? 4) Because of the idiosyncrasies of the Jgit and Egit projects, I wonder how many developers work on both projects?
Thanks a lot for helping me out. Best MoritzPs. This mail also went to the egit mailing list. Sorry for the double post if you are in both lists.
Back to the top