Building Knowledge through Families of Experiments
IEEE Transactions on Software Engineering
Parallel changes in large-scale software development: an observational case study
ACM Transactions on Software Engineering and Methodology (TOSEM)
Software Configuration Management Patterns: Effective Teamwork, Practical Integration
Software Configuration Management Patterns: Effective Teamwork, Practical Integration
Ethical Issues in Empirical Studies of Software Engineering
IEEE Transactions on Software Engineering
Palantír: raising awareness among configuration management workspaces
Proceedings of the 25th International Conference on Software Engineering
Conducting On-line Surveys in Software Engineering
ISESE '03 Proceedings of the 2003 International Symposium on Empirical Software Engineering
FASTDash: a visual dashboard for fostering awareness in software teams
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Mining Workspace Updates in CVS
MSR '07 Proceedings of the Fourth International Workshop on Mining Software Repositories
Palantir: enhancing configuration management systems with workspace awareness to detect and resolve emerging conflicts
Empirical evidence of the benefits of workspace awareness in software configuration management
Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering
The promises and perils of mining git
MSR '09 Proceedings of the 2009 6th IEEE International Working Conference on Mining Software Repositories
Proceedings of the 2010 ICSE Workshop on Cooperative and Human Aspects of Software Engineering
Configuration Management Best Practices: Practical Methods that Work in the Real World
Configuration Management Best Practices: Practical Methods that Work in the Real World
Branching and merging: an investigation into current version control practices
Proceedings of the 4th International Workshop on Cooperative and Human Aspects of Software Engineering
A theory of branches as goals and virtual teams
Proceedings of the 4th International Workshop on Cooperative and Human Aspects of Software Engineering
Proceedings of the 2011 International Conference on Software and Systems Process
Failure is a four-letter word: a parody in empirical research
Proceedings of the 7th International Conference on Predictive Models in Software Engineering
Proactive detection of collaboration conflicts
Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering
An integration resolution algorithm for mining multiple branches in version control systems
ICSM '11 Proceedings of the 2011 27th IEEE International Conference on Software Maintenance
Cohesive and isolated development with branches
FASE'12 Proceedings of the 15th international conference on Fundamental Approaches to Software Engineering
1st international workshop on release engineering (RELENG 2013)
Proceedings of the 2013 International Conference on Software Engineering
Will my patch make it? and how fast?: case study on the Linux kernel
Proceedings of the 10th Working Conference on Mining Software Repositories
| Hi-index | 0.00 |
Branches within source code management systems (SCMs) allow a software project to divide work among its teams for concurrent development by isolating changes. However, this benefit comes with several costs: increased time required for changes to move through the system and pain and error potential when integrating changes across branches. In this paper, we present the results of a survey to characterize how developers use branches in a large industrial project and common problems that they face. One of the major problems mentioned was the long delay that it takes changes to move from one team to another, which is often caused by having too many branches (branchmania). To monitor branch health, we introduce a novel what-if analysis to assess alternative branch structures with respect to two properties, isolation and liveness. We demonstrate with several scenarios how our what-if analysis can support branch decisions. By removing high-cost-low-benefit branches in Windows based on our what-if analysis, changes would each have saved 8.9 days of delay and only introduced 0.04 additional conflicts on average.