How the adoption of feature toggles correlates with branch merges and defects in open-source projects?
Eduardo Smil Prutchi, Heleno de Souza Campos Junior, Leonardo Gresta, Paulino Murta

TL;DR
This study investigates how adopting feature toggles affects branch merging complexity and defect rates in open-source projects, revealing a reduction in merge effort but an increase in defect fixing time, with inconclusive causality.
Contribution
It provides empirical evidence on the impact of feature toggles on merging and defect metrics across multiple programming languages in open-source projects.
Findings
Reduction in merge effort after feature toggle adoption
Increase in total defect fixing time post-adoption
No confirmed causal link between feature toggles and defect fixing time
Abstract
Context: Branching has been widely adopted in version control to enable collaborative software development. However, the isolation caused by branches may impose challenges on the upcoming merging process. Recently, companies like Google, Microsoft, Facebook, and Spotify, among others, have adopted trunk-based development together with feature toggles. This strategy enables collaboration without the need for isolation through branches, potentially reducing the merging challenges. However, the literature lacks evidence about the benefits and limitations of feature toggles to collaborative software development. Objective/Method: In this paper, we study the effects of applying feature toggles on 949 open-source projects written in 6 different programming languages. We first identified the moment in which each project adopted a feature toggles framework. Then, we observed whether the…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
