This document discusses version control systems and their usefulness for elearning development. It explains what version control is, why it is important for elearning projects, and demonstrates how version control systems track changes and allow collaboration in a way that prevents overwriting files. Specific version control systems like Subversion and tools like TortoiseSVN are presented. The document encourages adopting version control and provides resources for setting up systems.

1. Gates Matthew Stoner University of Arizona [email_address] Version Control in elearning development

3. Quick Poll: How many times have you overwritten a file you made and regretted it instantly?

8. Lingo Repository The database in which files are stored Subversion Server The computer storing & hosting the repository

9. Lingo Working Set/Working Copy Local directory where you make changes Trunk/Main The primary location for code in the repository

17. production Example Darin web developer Jane graphic artist Step 1. Darin develops some course web pages Step 2. Darin commits to repository Step 3. Jane creates graphics & media for the course Step 4. Jane checks out Darin’s files from repository Step 5. Jane inserts media into webpages Step 6. Jane commits changes to repository

18. production Example Sally Instructor Step 7. Jordan reviews course before deployment to development server Step 8. Jordan deploys files to development server Step 9. Sally reviews course web site and suggests changes Step 10. Darin makes changes and commits new version to repository for review and deployment Jordan supervisor

19. FTP Perspective intro.html 9-1-2009 12:05 pm glosssary.html 9-1-2009 12:05 pm activity.html 9-1-2009 12:05 pm conclusion.html 9-1-2009 12:05 pm Typical file structure view for web pages uploaded to a server Darin uploads his web pages to the server

20. Subversion Perspective intro.html 9-1-2009 12:05 pm glosssary.html 9-1-2009 12:05 pm activity.html 9-1-2009 12:05 pm conclusion.html 9-1-2009 12:05 pm Similar to FTP view, but meta data is stored as to whom committed the files and any notes they added v1 Darin uploads his web pages to the repository r1

21. FTP Perspective intro.html 9-3-2009 2:05 pm glosssary.html 9-2-2009 10:33 am activity.html 9-3-2009 2:15 pm conclusion.html 9-1-2009 12:05 pm File save times reflect changes on server but no meta information If anyone updated the files between the time Jane retrieved them, those changes are lost Jane downloads files from server and makes her changes graphics 9-3-2009 2:05 pm

22. Subversion View Darin’s files remain unchanged in revision 2, but the graphics folder is added Jane commits the graphics to the repository r2 graphics 9-3-2009 2:05 pm intro.html 9-1-2009 12:05 pm glosssary.html 9-1-2009 12:05 pm activity.html 9-1-2009 12:05 pm conclusion.html 9-1-2009 12:05 pm

23. Subversion View New versions of Darin’s files are committed to the database, but originals remain in database Jane commits updated web pages to the repository r3 intro.html 9-3-2009 2:05 pm glosssary.html 9-2-2009 10:33 am activity.html 9-3-2009 2:15 pm conclusion.html 9-1-2009 12:05 pm graphics 9-3-2009 2:05 pm

25. Are you ready to take the plunge?

32. Conflicts http://betterexplained.com/articles/a-visual-guide-to-version-control/

34. Advanced Concepts http://betterexplained.com/articles/a-visual-guide-to-version-control/

36. Some Hosting Services

39. Quick Poll: Who is planning to implement version control for their production environment?