在开源项目中，特性切换的采用与分支合并和缺陷有什么关系？
How the adoption of feature toggles correlates with branch merges and defects in open-source projects?
摘要：
背景：分支在版本控制中被广泛采用，以支持协作软件开发。然而，分支造成的隔离可能会对即将到来的合并过程带来挑战。最近，像谷歌、微软、Facebook和Spotify等公司已经采用了基于主干的开发以及功能切换。此策略支持协作，而无需通过分支进行隔离，从而可能减少合并的挑战。然而，文献缺乏证据的好处和限制功能切换协作软件开发。目的/方法：在本文中，我们研究的影响，应用功能切换949个开源项目写在6个不同的程序设计语言。我们首先确定了每个项目采用功能切换框架的时刻。然后，我们观察采用是否意味着分支合并的频率或复杂性以及缺陷数量的显着变化，以及修复它们的平均时间。最后，我们比较了从一组控制项目，不使用功能切换框架获得的结果。结果/结论：我们可以观察到，在采用特性切换框架之后，平均合并工作量减少，修复缺陷所需的平均总时间增加。然而，我们无法确认这种增加是受到使用功能切换的影响。
英文摘要：
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 adoption implied significant changes in the frequency or complexity of branch merges and the number of defects, and the average time to fix them. Finally, we compared the obtained results with results obtained from a set of control projects that do not use feature toggles frameworks. Results/Conclusion: We could observe a reduction in the average merge effort and an increase in the average total time needed to fix defects after adopting feature toggles frameworks. However, we could not confirm that this increase was influenced by the use of feature toggles.
机构、总结、中文摘要均由AI分析而来，可能存在错误，请以论文正文为准。
