Abstract
It has been observed that allowing source code changes to be made only after source code reviews has a positive impact on the quality and lifetime of the resulting software. In some cases, code review processes take quite a long time and this negatively affects software development costs and employee job satisfaction. Establishing mechanisms that predict what kind of feedback reviewers will provide and what revisions they will ask for can reduce the number of times this problem occurs. Thanks to such mechanisms, developers can improve the maturity of their code change requests before the review process starts. In this way, when they start the review, the process may advance quickly and more smoothly. In this study, as a first step towards this goal, we developed a mechanism to identify whether a change proposal would require any revisions or not for approval.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: TURKISH JOURNAL OF ELECTRICAL ENGINEERING & COMPUTER SCIENCES
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
