%0 Conference Paper %1 Brindescu:2014:CDV:2568225.2568322 %A Brindescu, Caius %A Codoban, Mihai %A Shmarkatiuk, Sergii %A Dig, Danny %B Proceedings of the 36th International Conference on Software Engineering %C New York, NY, USA %D 2014 %I ACM %K version-control %P 322--333 %R 10.1145/2568225.2568322 %T How Do Centralized and Distributed Version Control Systems Impact Software Changes? %U http://doi.acm.org/10.1145/2568225.2568322 %X Distributed Version Control Systems (DVCS) have seen an increase in popularity relative to traditional Centralized Version Control Systems (CVCS). Yet we know little on whether developers are benefitting from the extra power of DVCS. Without such knowledge, researchers, developers, tool builders, and team managers are in the danger of making wrong assumptions. In this paper we present the first in-depth, large scale empirical study that looks at the influence of DVCS on the practice of splitting, grouping, and committing changes. We recruited 820 participants for a survey that sheds light into the practice of using DVCS. We also analyzed 409M lines of code changed by 358300 commits, made by 5890 developers, in 132 repositories containing a total of 73M LOC. Using this data, we uncovered some interesting facts. For example, (i) commits made in distributed repositories were 32% smaller than the centralized ones, (ii) developers split commits more often in DVCS, and (iii) DVCS commits are more likely to have references to issue tracking labels. %@ 978-1-4503-2756-5

@inproceedings{Brindescu:2014:CDV:2568225.2568322, abstract = {Distributed Version Control Systems (DVCS) have seen an increase in popularity relative to traditional Centralized Version Control Systems (CVCS). Yet we know little on whether developers are benefitting from the extra power of DVCS. Without such knowledge, researchers, developers, tool builders, and team managers are in the danger of making wrong assumptions. In this paper we present the first in-depth, large scale empirical study that looks at the influence of DVCS on the practice of splitting, grouping, and committing changes. We recruited 820 participants for a survey that sheds light into the practice of using DVCS. We also analyzed 409M lines of code changed by 358300 commits, made by 5890 developers, in 132 repositories containing a total of 73M LOC. Using this data, we uncovered some interesting facts. For example, (i) commits made in distributed repositories were 32% smaller than the centralized ones, (ii) developers split commits more often in DVCS, and (iii) DVCS commits are more likely to have references to issue tracking labels.}, acmid = {2568322}, added-at = {2020-08-31T02:27:51.000+0200}, address = {New York, NY, USA}, author = {Brindescu, Caius and Codoban, Mihai and Shmarkatiuk, Sergii and Dig, Danny}, biburl = {https://www.bibsonomy.org/bibtex/29a41165356ac294eab1ab781e811fbc3/gbschenkel}, booktitle = {Proceedings of the 36th International Conference on Software Engineering}, description = {How do centralized and distributed version control systems impact software changes?}, doi = {10.1145/2568225.2568322}, interhash = {144260da68085e9ca6e24de4239d9d22}, intrahash = {9a41165356ac294eab1ab781e811fbc3}, isbn = {978-1-4503-2756-5}, keywords = {version-control}, location = {Hyderabad, India}, numpages = {12}, pages = {322--333}, publisher = {ACM}, series = {ICSE 2014}, timestamp = {2020-08-31T02:27:51.000+0200}, title = {How Do Centralized and Distributed Version Control Systems Impact Software Changes?}, url = {http://doi.acm.org/10.1145/2568225.2568322}, year = 2014 }