skip to main content
10.1145/2382456.2382510acmconferencesArticle/Chapter ViewAbstractPublication PagesuccsConference Proceedingsconference-collections
research-article

Modern version control: creating an efficient development ecosystem

Published:15 October 2012Publication History

ABSTRACT

In 2011, Santa Clara University School of Law Technology and Academic Computing (LTAC) identified that its version control system could greatly benefit from the use of modern source control management software. Source code for high value projects, such as the Santa Clara Law website, were previously held in a Subversion (SVN) repository in a client-server model, providing version control and redundancy. Because of the resource footprint associated with SVN, only projects with high importance could be setup with version control. As more web-based applications were introduced, the need for a more efficient revision control system arose. Git, a highly efficient decentralized version control system (DVCS), was selected after evaluating similar technologies. This change transformed the entire development process, making the development cycle more streamlined and with greater flexibility. In the early use of Git, LTAC also discovered its use as a deployment tool, increasing redundancy on servers and reducing overhead usually associated with revision control. It also serves as the vital link between LTAC's issue tracking system, Redmine, and the development team. The introduction of Redmine has helped LTAC monitor website issues, manage projects, and continually review changes to the code base. LTAC has created a development ecosystem that provides redundancy and accountability using open source products that carry no cost. Git has significant performance gains over SVN, making its integration and use less frustrating and distracting for developers. Redmine gives developers and customers the opportunity to organize, track, and resolve issues. The flexibility of the technology used means that any project, from a content management system to a one-off script, can benefit from source control without large costs or long deployment times.

References

  1. APPLE, INC. 2012. Apple - Auto Save and Versions - Every edit and rewrite. Saved. http://www.apple.com/macosx/whats-new/auto-save.htmlGoogle ScholarGoogle Scholar
  2. berliOS. 2012. SCCS - The POSIX standard Source Code Control System. http://sccs.berlios.de/Google ScholarGoogle Scholar
  3. GNU. 2012. GNU RCS - GNU Project - Free Software Foundation (FSF). http://www.gnu.org/software/rcs/Google ScholarGoogle Scholar
  4. GNU. 1995. CCVS Revision Log http://cvs.savannah.gnu.org/viewvc/ccvs/NEWS?revision=1.1&root=cvs&view=markupGoogle ScholarGoogle Scholar
  5. Collins-Sussman, Ben; Brian W. Fitzpatrick; C. Michael Pilato. 2011. Version Control with Subversion (for Subversion 1.7). http://svnbook.red-bean.com/en/1.7/svn.intro.whatis.html#svn.intro.historyGoogle ScholarGoogle Scholar
  6. LKML. 1998. LKML: (Larry McVoy): A solution for growing pains. https://lkml.org/lkml/1998/9/30/122Google ScholarGoogle Scholar
  7. Jeremy Andrews. 2005. Feature: No More Free BitKeeper. http://kerneltrap.org/node/4966Google ScholarGoogle Scholar
  8. Linus Torvalds. 2005. 'Re: Kernel SCM saga..' -- MARC http://marc.info/?l=linux-kernel&m=111288700902396Google ScholarGoogle Scholar

Index Terms

  1. Modern version control: creating an efficient development ecosystem

        Recommendations

        Comments

        Login options

        Check if you have access through your login credentials or your institution to get full access on this article.

        Sign in
        • Published in

          cover image ACM Conferences
          SIGUCCS '12: Proceedings of the 40th annual ACM SIGUCCS conference on User services
          October 2012
          262 pages
          ISBN:9781450314947
          DOI:10.1145/2382456

          Copyright © 2012 ACM

          Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

          Publisher

          Association for Computing Machinery

          New York, NY, United States

          Publication History

          • Published: 15 October 2012

          Permissions

          Request permissions about this article.

          Request Permissions

          Check for updates

          Qualifiers

          • research-article

          Acceptance Rates

          Overall Acceptance Rate123of170submissions,72%
        • Article Metrics

          • Downloads (Last 12 months)30
          • Downloads (Last 6 weeks)8

          Other Metrics

        PDF Format

        View or Download as a PDF file.

        PDF

        eReader

        View online with eReader.

        eReader