The impact of tangled code changes
By Kim Herzig, Andreas Zeller. IEEE Working Conference on Mining Software Repositories, 2013
308 citations recorded by the source corpus.
Subfields: Computer Networks and Communications, Information Systems, Software
View Paper: https://www.semanticscholar.org/paper/390ef1df3f3552e6d17b34d25bb1dcb783272cc6
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Computer Networks and Communications
- Baishakhi Ray
- Alberto Bacchelli
- Premkumar T. Devanbu
- Vincent J. Hellendoorn
- David Lo
- Zhaopeng Tu
- Saheel Godhane
- Margaret-Anne D. Storey
In Information Systems
- Premkumar T. Devanbu
- Baishakhi Ray
- Vincent J. Hellendoorn
- Alberto Bacchelli
- Georgios Gousios
- Charles Sutton
- Saikat Chakraborty
- Yangruibo Ding
In Software
- Vincent J. Hellendoorn
- Baishakhi Ray
- Premkumar T. Devanbu
- Yangruibo Ding
- Alberto Bacchelli
- Georgios Gousios
- Zhaopeng Tu
- David Lo
Citations in the corpus
- Work Practices and Challenges in Pull-Based Development: The Contributor's Perspective (2014, background): “Recently, researchers have proposed automated approaches to split changes into self-contained tasks [29, 13].”
- On the "Naturalness" of Buggy Code (2015, background): “[21] showed that around 17% of all source files are incorrectly associated with bugs due to such tangled changes.”
- History Driven Program Repair (2016, background): “Commits that satisfy the first condition but involve many changed lines typically include changes beyond the bug fix, addressing feature addition, refactoring, etc [18], [23].”
- Deep Learning Based Vulnerability Detection: Are We There Yet? (2020, background): “Developers often combine more than one unrelated or weakly related changes in code in one commit [60] causing such a commit to be entanglement of more than one changes.”