Who should make decision on this pull request? Analyzing time-decaying relationships and file similarities for integrator prediction
暂无分享,去创建一个
Yun Yang | David Lo | Xin Xia | Li Zhang | Jing Jiang | Jiateng Zheng | Xin Xia | Jing Jiang | D. Lo | Jiateng Zheng | Yun Yang | Li Zhang
[1] Premkumar T. Devanbu,et al. Will They Like This? Evaluating Code Contributions with Language Models , 2015, 2015 IEEE/ACM 12th Working Conference on Mining Software Repositories.
[2] David Lo,et al. Accurate developer recommendation for bug resolution , 2013, 2013 20th Working Conference on Reverse Engineering (WCRE).
[3] Darko Marinov,et al. Usage, costs, and benefits of continuous integration in open-source projects , 2016, 2016 31st IEEE/ACM International Conference on Automated Software Engineering (ASE).
[4] James D. Herbsleb,et al. Let's talk about it: evaluating contributions through discussion in GitHub , 2014, SIGSOFT FSE.
[5] Georgios Gousios,et al. Work practices and challenges in pull-based development: the contributor's perspective , 2015, ICSE.
[6] Vipin Balachandran,et al. Reducing human effort and improving quality in peer code reviews using automatic static analysis and reviewer recommendation , 2013, 2013 35th International Conference on Software Engineering (ICSE).
[7] Denys Poshyvanyk,et al. Journal of Software Maintenance and Evolution: Research and Practice Assigning Change Requests to Software Developers , 2022 .
[8] James D. Herbsleb,et al. Influence of social and technical factors for evaluating contribution in GitHub , 2014, ICSE.
[9] Gang Yin,et al. Determinants of pull-based development in the context of continuous integration , 2016, Science China Information Sciences.
[10] Qingsheng Zhu,et al. Fluctuation-Aware and Predictive Workflow Scheduling in Cost-Effective Infrastructure-as-a-Service Clouds , 2018, IEEE Access.
[11] Mario Linares Vásquez,et al. Triaging incoming change requests: Bug or commit history, or code authorship? , 2012, 2012 28th IEEE International Conference on Software Maintenance (ICSM).
[12] Ye Yang,et al. DREX: Developer Recommendation with K-Nearest-Neighbor Search and Expertise Ranking , 2011, 2011 18th Asia-Pacific Software Engineering Conference.
[13] Katsuro Inoue,et al. Search-Based Peer Reviewers Recommendation in Modern Code Review , 2016, 2016 IEEE International Conference on Software Maintenance and Evolution (ICSME).
[14] Chanchal Kumar Roy,et al. Predicting Usefulness of Code Review Comments Using Textual Features and Developer Experience , 2017, 2017 IEEE/ACM 14th International Conference on Mining Software Repositories (MSR).
[15] Denys Poshyvanyk,et al. Amalgamating source code authors, maintainers, and change proneness to triage change requests , 2014, ICPC 2014.
[16] Gang Yin,et al. Reviewer Recommender of Pull-Requests in GitHub , 2014, 2014 IEEE International Conference on Software Maintenance and Evolution.
[17] Alberto Bacchelli,et al. Expectations, outcomes, and challenges of modern code review , 2013, 2013 35th International Conference on Software Engineering (ICSE).
[18] Thomas Zimmermann,et al. Improving bug triage with bug tossing graphs , 2009, ESEC/FSE '09.
[19] Gail C. Murphy,et al. Who should fix this bug? , 2006, ICSE.
[20] Premkumar T. Devanbu,et al. Quality and productivity outcomes relating to continuous integration in GitHub , 2015, ESEC/SIGSOFT FSE.
[21] Chanchal Kumar Roy,et al. CORRECT: Code Reviewer Recommendation in GitHub Based on Cross-Project and Technology Experience , 2016, 2016 IEEE/ACM 38th International Conference on Software Engineering Companion (ICSE-C).
[22] Hao Hu,et al. Effective Bug Triage Based on Historical Bug-Fix Information , 2014, 2014 IEEE 25th International Symposium on Software Reliability Engineering.
[23] Jia-Huan He,et al. Who should comment on this pull request? Analyzing attributes for more accurate commenter recommendation in pull-based development , 2017, Inf. Softw. Technol..
[24] Jesús M. González-Barahona,et al. Contributor Turnover in Libre Software Projects , 2006, OSS.
[25] Christian Bird,et al. Automatically Recommending Peer Reviewers in Modern Code Review , 2016, IEEE Transactions on Software Engineering.
[26] Hajimu Iida,et al. Who should review my code? A file location-based code-reviewer recommendation approach for Modern Code Review , 2015, 2015 IEEE 22nd International Conference on Software Analysis, Evolution, and Reengineering (SANER).
[27] Gail C. Murphy,et al. Automatic bug triage using text categorization , 2004, SEKE.
[28] Jia-Huan He,et al. CoreDevRec: Automatic Core Member Recommendation for Contribution Evaluation , 2015, Journal of Computer Science and Technology.
[29] Gang Yin,et al. Reviewer recommendation for pull-requests in GitHub: What can we learn from code review and bug assignment? , 2016, Inf. Softw. Technol..
[30] Arie van Deursen,et al. An exploratory study of the pull-based software development model , 2014, ICSE.
[31] David Lo,et al. Who should review this change?: Putting text and file location analyses together for more accurate recommendations , 2015, 2015 IEEE International Conference on Software Maintenance and Evolution (ICSME).
[32] Weiqiang Zhang,et al. Developer social networks in software engineering: construction, analysis, and applications , 2014, Science China Information Sciences.
[33] Volker Gruhn,et al. Automatically recommending code reviewers based on their expertise: An empirical comparison , 2016, 2016 31st IEEE/ACM International Conference on Automated Software Engineering (ASE).
[34] Oscar Nierstrasz,et al. Assigning bug reports using a vocabulary-based expertise model of developers , 2009, 2009 6th IEEE International Working Conference on Mining Software Repositories.
[35] Zhendong Niu,et al. Schedule of Bad Smell Detection and Resolution: A New Way to Save Effort , 2012, IEEE Transactions on Software Engineering.