Assessing the value of branches with what-if analysis
The DOI matches its Crossref record; 3 of the 3 references it cites were found in a registry or an index.
Abstract
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.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Five misunderstandings about case-study research
Flyvbjerg, B. (2006) · Qualitative Inquiry · doi:10.1177/1077800405284363 · Cited by 14,266
The promises and perils of mining git
Bird, C., Rigby, P. C., Barr, E. T., Hamilton, D. J., German, D. M., & Devanbu, P. (2009) · 2009 6th IEEE International Working Conference on Mining Software Repositories · doi:10.1109/msr.2009.5069475 · Cited by 311
Self-citationConducting on-line surveys in software engineering
Punter, T., Ciolkowski, M., Freimut, B., & John, I. (2003) · 2003 International Symposium on Empirical Software Engineering, 2003. ISESE 2003. Proceedings. · doi:10.1109/isese.2003.1237967 · Cited by 193 · cited 1×
“6% response rate) without sending any reminders; other online surveys in software engineering have reported response rates ranging from 14% to 20% [9].”
Background
Cited by
An exploratory study of the pull-based software development model
Gousios, G., Pinzger, M., & Deursen, A. V. (2014) · Proceedings of the 36th International Conference on Software Engineering · doi:10.1145/2568225.2568260 · Cited by 628
“, an organized way to inspect and test contributions before those are merged to the main development branch [7].”
BackgroundInfluentialWork practices and challenges in pull-based development: the contributor's perspective
Gousios, G., Storey, M.-A., & Bacchelli, A. (2016) · Proceedings of the 38th International Conference on Software Engineering · doi:10.1145/2884781.2884826 · Cited by 335
An Empirical Study of RefactoringChallenges and Benefits at Microsoft
Kim, M., Zimmermann, T., & Nagappan, N. (2014) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2014.2318734 · Cited by 231
““Cross-branch integration was the biggest problem [15].”
Self-citationEarly Detection of Collaboration Conflicts and Risks
Brun, Y., Holmes, R., Ernst, M. D., & Notkin, D. (2013) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2013.28 · Cited by 82
“In practice, some branches can cause delays in integration, in part because branches typically have to meet certain criteria before integration [2], [6].”
BackgroundUnderstanding semi-structured merge conflict characteristics in open-source Java projects
Accioly, P., Borba, P., & Cavalcanti, G. (2018) · Empirical Software Engineering · doi:10.1007/s10664-017-9586-1 · Cited by 48
Metadata
- Authors
- Bird, C., & Zimmermann, T.
- Venue
- Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering
- Publisher
- ACM
- Published
- 2012-11-11
- Pages
- 1-11
- OpenAlex
- W1995969252
- Cited by
- 114
- References
- 3
- FWCI
- 9.10
- Type
- conference paper
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Assessing the value of branches with what-if analysis. https://app.cochat.ai/papers/10.1145/2393596.2393648
- The paper
- Bird, C., & Zimmermann, T. (2012). Assessing the value of branches with what-if analysis. Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering. https://doi.org/10.1145/2393596.2393648
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.