A State-of-the-Art Survey on Software Merging
IEEE Transactions on Software Engineering
Continuous Integration: Improving Software Quality and Reducing Risk (The Addison-Wesley Signature Series)
Branching and merging in the repository
Proceedings of the 2008 international working conference on Mining software repositories
A Hundred Days of Continuous Integration
AGILE '08 Proceedings of the Agile 2008
Why are software projects moving from centralized to decentralized version control systems?
CHASE '09 Proceedings of the 2009 ICSE Workshop on Cooperative and Human Aspects on Software Engineering
Making Sense of Revision-control Systems
Queue - File Systems
Proceedings of the ACM 2012 conference on Computer Supported Cooperative Work
Proceedings of the WICSA/ECSA 2012 Companion Volume
Assessing the value of branches with what-if analysis
Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering
Hi-index | 0.00 |
The use of version control has become ubiquitous in software development projects. Version control systems facilitate parallel development and maintenance through branching, the creation of isolated codelines. Merging is a consequence of branching and is the process of integrating codelines. However, there are unanswered questions about the use of version control to support parallel development; in particular, how are branching and merging used in practice? What defines a successful branching and merging strategy? As a first step towards answering these questions, we recruited a diverse sample of 140 version control users to participate in an online survey. In this paper, we present the survey results and 4 key observations about branching and merging practices in software development projects.