Migration from Subversion to Git Version Control System

Authors

  • Varshney M Department of Computer Science, Mewar University, Chittorgarh (Raj), India
  • Shrivastava AK Department of Computer Science, Mewar University, Chittorgarh (Raj), India
  • Aggarwal A School of Computer Science, University of Petroleum & Energy Studies, Dehradun, India
  • Kumar A School of Computer Science, University of Petroleum & Energy Studies, Dehradun, India

DOI:

https://doi.org/10.26438/ijcse/v6i12.768771

Keywords:

Version control system, distributed VCS, centralized VCS, transition, branching, merging, time, space

Abstract

In recent years, software development in software industries is getting a transition from centralized version control systems (CVCSs) like subversion, mercurial, perforce, CVS etc. to decentralized version control systems (DVCSs) like Git due to a number of reasons like time, space, branching, merging, offline commits & builds and repository etc. Both centralized VCSs and distributed VCSs have gone through ample investigations in recent past but individually from the software developer’s point of view in a large commercial software industry. There has been a little focus on the transition across Git having a share of more than three-fourth of total VCS, and Subversion having a share of 13.5%. In this work transition process from Subversion VCS to Git VCS has been investigated.

References

[1] N. B. Ruparelia. “The history of version control,” ACM SIGSOFT Software Engineering Notes vol. 35, no. 1, pp. 5-9, 2010.

[2] B. De Alwis and J. Sillito, “Why are software projects moving from centralized to decentralized version control systems?” ICSE Workshop on Cooperative and Human Aspects on Software Engineering (CHASE'09), pp. 36-39, 2009.

[3] D. Spinellis. “Git,” IEEE Software, vol. 29, no. 3, pp. 100-101, 2012.

[4] https://www2.physics.ox.ac.uk/it-services/moving-projectsfrom-svn-to-git

[5] https://stosb.com/static/talks/case_study_git_efl_linuxcon_eu_13 .pdf

[6] Loeliger, J., Matthew McCullough, “Version Control with Git: Powerful Tools and Techniques for Collaborative Software Development,” O’Reilly Media, Inc. Second Edition, 2009.

[7] Tom De Nies, Sara Magliacane, Ruben Verborgh, Sam Coppens,

Paul Groth, Erik Mannens, and Rik Van de Walle, “Git2PROV: Exposing Version Control System Content as W3C PROV,” Proc. 12th Int. Semantic Web Conf., pp. 1-4, Oct. 2013.

[8] C. Brindescu, M. Codoban, S. Shmarkatiuk and D. Dig, "How Do Centralized and Distributed Version Control Systems Impact Software Changes?," Proc. 36th Int. Conf. on Software Engineering, Hyderabad, India, pp. 322-333, 2014.

[9] Kıvanç Muşlu, Christian Bird, Nachiappan Nagappan, Christian Bird, “Transition from Centralized to Decentralized Version Control Systems: A Case Study on Reasons, Barriers, and Outcomes,” Proc. Int. Conf. on Software Engineering ICSE2014, pp. 334-344, May 31- June 7, Hyderabad, India, 2014.

[10] Christian Bird, Peter C. Rigby, Earl T. Barr, David J. Hamilton, Daniel M. German, Prem Devanbu, “The Promises and Perils of Mining Git,” Proc. 6th IEEE International Working Conference on Mining Software Repositories, Vancouver, BC, Canada, May 16-17, pp. 1-10, 2009

[11] E. T. Barr, C. Bird, P. C. Rigby, A. Hindle, D. M. German and D. Premkumar, "Cohesive and Isolated Development with Branches," Proc. 15th International Conference on Fundamental Approaches to Software Engineering, Tallinn, Estonia, pp. 316331, March 24 - April 01, 2012.

Downloads

Published

2018-12-31
CITATION
DOI: 10.26438/ijcse/v6i12.768771
Published: 2018-12-31

How to Cite

[1]
M. Varshney, A. K. Shrivastava, A. Aggarwal, and A. Kumar, “Migration from Subversion to Git Version Control System”, Int. J. Comp. Sci. Eng., vol. 6, no. 12, pp. 768–771, Dec. 2018.

Issue

Vol. 6 No. 12 (2018): IJCSE December Editor

Section

Research Article

License

Creative Commons License

This work is licensed under a Creative Commons Attribution 4.0 International License.

Authors contributing to this journal agree to publish their articles under the Creative Commons Attribution 4.0 International License, allowing third parties to share their work (copy, distribute, transmit) and to adapt it, under the condition that the authors are given credit and that in the event of reuse or distribution, the terms of this license are made clear.