A Two-Person Inspection Method to Improve Programming Productivity
IEEE Transactions on Software Engineering
Does every inspection need a meeting?
SIGSOFT '93 Proceedings of the 1st ACM SIGSOFT symposium on Foundations of software engineering
Understanding the sources of variation in software inspections
ACM Transactions on Software Engineering and Methodology (TOSEM)
Communications of the ACM
IEEE Transactions on Software Engineering
Two case studies of open source software development: Apache and Mozilla
ACM Transactions on Software Engineering and Methodology (TOSEM)
The Cathedral and the Bazaar
Expertise browser: a quantitative approach to identifying expertise
Proceedings of the 24th International Conference on Software Engineering
Lessons from Three Years of Inspection Data
IEEE Software
A history of software inspections
Software pioneers
Controlling Software Projects: Management, Measurement, and Estimates
Controlling Software Projects: Management, Measurement, and Estimates
Continuous Integration: Improving Software Quality and Reducing Risk (The Addison-Wesley Signature Series)
Patch Review Processes in Open Source Software Development Communities: A Comparative Case Study
HICSS '07 Proceedings of the 40th Annual Hawaii International Conference on System Sciences
Detecting Patch Submission and Acceptance in OSS Projects
MSR '07 Proceedings of the Fourth International Workshop on Mining Software Repositories
Open source software peer review practices: a case study of the apache server
Proceedings of the 30th international conference on Software engineering
The role of patch review in software evolution: an analysis of the mozilla firefox
Proceedings of the joint international and annual ERCIM workshops on Principles of software evolution (IWPSE) and software evolution (Evol) workshops
Design and code inspections to reduce errors in program development
IBM Systems Journal
Understanding broadcast based peer review on open source software projects
Proceedings of the 33rd International Conference on Software Engineering
Understanding open source software peer review: review processes, parameters and statistical models, and underlying behaviours and mechanisms
Expectations, outcomes, and challenges of modern code review
Proceedings of the 2013 International Conference on Software Engineering
Gerrit software code review data from Android
Proceedings of the 10th Working Conference on Mining Software Repositories
| Hi-index | 0.00 |
Software peer review is practiced on a diverse set of software projects that have drastically different settings, cultures, incentive systems, and time pressures. In an effort to characterize and understand these differences we examine two Google-led projects, Android and Chromium OS, three Microsoft projects, Bing, Office, and MS SQL, and projects internal to AMD. We contrast our findings with data taken from traditional software inspection conducted on a Lucent project and from open source software peer review on six projects, including Apache, Linux, and KDE. Our measures of interest include the review interval, the number of developers involved in review, and proxy measures for the number of defects found during review. We find that despite differences among projects, many of the characteristics of the review process have independently converged to similar values which we think indicate general principles of code review practice. We also introduce a measure of the degree to which knowledge is shared during review. This is an aspect of review practice that has traditionally only had experiential support. Our knowledge sharing measure shows that conducting peer review increases the number of distinct files a developer knows about by 66% to 150% depending on the project. This paper is one of the first studies of contemporary review in software firms and the most diverse study of peer review to date.