Version control – Review

1. Version control – Review In session 13 (Monday) we learned: • What it is • Why we do it • How to do it

2. Version control:what is it? The repository stores the initial version of the software and all subsequent changes to it. Our repository is in the basement of Crapo. • A system that controls the successive versions of the software as it is developed Each team member has her own copy of the software, working on her own part of it. She periodically: updates to get changes from her teammates commits her own work to a new version in the repository

3. Version control – why we do it • It allows the software development team to: • Produce successive versions of the software • And fall back to a previous version if necessary • Work concurrently on the software • Work on different branches of the software development • We use version control in CSSE 120 because: • It allows you to work more easily with your teammates • It is a practice that scales up to larger software projects • The larger the project, the more important version control becomes

4. Version control – what we saw using it… • Teammates still had conflicts • Brings up the question – How would things be going right now without CVS?

5. Version control – how to do it? Preliminary steps: Someone in the organization creates the repository. It can contain many modules. Someone on the team does CVS ~ Make New Moduleto upload the initial version of the module to the repository You doCVS Checkoutto obtain that initial version of the module Getting it from the server – do this! • You repeatedly: • 1. CVS Update • 2. Work on the software • Occasionally do CVS Update to get your teammate’s work • CVS warns you if that work conflicts with your own work • 3. Share your work (put it into the repository, as a new version) when you are ready, by: • a. CVS Update • b. CVS Add Contents • c. CVS Commit Putting it back on the server – do these 3 steps!