Subversion is a version control system. With subversion, you keep a master copy of your project on a server, plus you can keep a copy on each computer that you use to work on the project. (For example, I have a master copy of these web pages on the server, plus a copy on each of the three computers that I typically work on). If you are working on a pair project, you might keep one copy on each partner's machine.

Terminology: the location of the master copy is called the repository and the local copy is called working copy.

To use subversion, you must remember exactly two things:

There's more, but that's the basic idea.

By using subversion, not only can you and your partner avoid discrepencies between your copies of the project, but you can also revert to earlier versions if you need to, etc.

Because you always keep a master copy on the server, you never have to e-mail each other copies of the project, etc.

Subversion (and other version control systems) become even more valuable when there are many people working on a project, perhaps from many different places. In a company setting, this is vital, and there are often restrictions on who can check files into the master copy of a project. Luckily we don't have to worry about these complications.

Your subversion repository (master copy) will be at
for your number NNN.

You will turn in your homework by leaving it on the subversion server.

You can check whether your homework is visible by pointing your Web browser at the URL above. The browser will prompt you for a username and a password and, if these are correct, will display your directory structure as a Web page.

Just like the design recipe asks you to run tests at the end of a design cycle, you should -- no you must -- check on your homework assignment on the server at the end of every work session.

Last modified: Fri Jan 09 12:59:02 Eastern Standard Time 2009