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.
- APPLE, INC. 2012. Apple - Auto Save and Versions - Every edit and rewrite. Saved. http://www.apple.com/macosx/whats-new/auto-save.htmlGoogle Scholar
- berliOS. 2012. SCCS - The POSIX standard Source Code Control System. http://sccs.berlios.de/Google Scholar
- GNU. 2012. GNU RCS - GNU Project - Free Software Foundation (FSF). http://www.gnu.org/software/rcs/Google Scholar
- GNU. 1995. CCVS Revision Log http://cvs.savannah.gnu.org/viewvc/ccvs/NEWS?revision=1.1&root=cvs&view=markupGoogle Scholar
- 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 Scholar
- LKML. 1998. LKML: (Larry McVoy): A solution for growing pains. https://lkml.org/lkml/1998/9/30/122Google Scholar
- Jeremy Andrews. 2005. Feature: No More Free BitKeeper. http://kerneltrap.org/node/4966Google Scholar
- Linus Torvalds. 2005. 'Re: Kernel SCM saga..' -- MARC http://marc.info/?l=linux-kernel&m=111288700902396Google Scholar
Index Terms
- Modern version control: creating an efficient development ecosystem
Recommendations
A Methodological Review Based Version Control System with Evolutionary Research for Software Processes
ICTCS '16: Proceedings of the Second International Conference on Information and Communication Technology for Competitive StrategiesThe constant add up of new features and bug fixes often make invariable changes and refinements inevitable in the software development at regular intervals. The software should enable the end-user to decipher the critical version information about the ...
Using version control in the classroom (abstract only)
SIGCSE '13: Proceeding of the 44th ACM technical symposium on Computer science educationProfessional software developers depend on version control every day and that dependency will continue to grow as advances in version control technology continue. Students with experience using version control are more prepared and qualified to work in ...
Comments