14. CM.Practice

This assignment involves using SVN over Google Code to set up and use projects.

1. Install a SVN client

Straightforward. I installed TortoiseSVN since I am using a Windows system. This took about 5 minutes.

2. Modify an existing Google Project.

This was also straightforward. I used CVS before and the checkout/commit process was pretty straightforward. The only part I didn't like was running verify before and after commits. This took about 15 minutes.

3. Create a new Google Hosting project.

This was where most of the time was spent. The first difficult was to find the actual link to create the project, since code.google.com does not provide an obvious link. Next, choosing a license was iffy, and I just copied what was chosen in the slides. It might be an interesting topic to discuss in class, however.

Finally, creating the discussion lists and commit lists was a pain since I had to go to Google Groups and create the lists, then go back to the project page and add them. If this was integrated into the project creation step, it would be easier (and less time consuming).

After the project setup I uploaded my files. Unfortunately, I messed up the first time (I uploaded it as a single folder) so I removed it. Then I uploaded up, then renamed the project folder to "trunk". It worked. However, afterwards I noticed the notes renamed the folder to 'trunk' before uploading it.

I wanted to avoid uploading the files individually since TortoiseSVN warned me that uploading the 11 files or so would cause 11 revisions.

This took about an hour.


Lessons Learned

Even the simplest thing can be a pain to set up, sometimes. Otherwise, I think the process was straightforward. Google could work a little on the interface for creating a project, but otherwise this was pretty trivial.