Lesson 03.2: Creating and Using a Subversion Repository

 

Summary

  • A repository lets you hold previous version of your program.
  • You have the ability to “revert” your program back to an older version, in case the current version does not work.
  • Save your changes to the repository after you add a new feature (and successfully test it).

 

Resources

Lesson 01.2: Installing SVN and VisualSVN

 

Return to main page

4 thoughts on “Lesson 03.2: Creating and Using a Subversion Repository

    1. You’re welcome. Source control is amazing – even for small, personal programs. Whenever I add a new feature (and confirm that it works), I save the program to the repository. Then, if my next change breaks something, I can easily go back to the last working version of the program.

  1. I’ve been learning Git and Github as a part of the original SuperAdventure tutorial – I just made a public repo on Github and started a separate branch for each chapter, then merged the changes back into master at the end of each chapter.

    This was very useful to learn source control practically. Using Git, it’s very easy to branch and merge, but you have to be careful or you end up applying and merging the wrong things. Thankfully if you commit many times with small sets of changes it’s not too hard to go back and reorder and reapply things correctly. In some ways it’s difficult, learning how to do it all the first time – much like learning a whole extra programming language. I’ve had to go through some web-based Git tutorials, training, and surf for answers on how to fix some of the problems I’ve created in the repo – all part of the learning process.

    Another way source control is useful is in making updates to the game without breaking the tutorial code – you can leave the original tutorial code untouched by creating a separate branch of the code to play around in or develop new features. By leaving the tutorial code separate and coming back to that branch just to work on new lessons, then it doesn’t break anything as the tutorial progresses. You can even merge new tutorial code down into the development branches if desired to keep them up-to-date with new tutorial features and refactors. It gets a little complicated at times, but that’s real-world programming, and basically how distributed, multi-person, and open-source projects seem to work.

    1. That’s a good way to work with projects. I use source control for all my projects, including my small personal projects. That’s especially true for these lessons. If the program works at the end of one lesson, it’s a good idea to commit the code to your source control. That way, if something breaks during the next lesson, it’s easy to go back to the previously-working version, or use the “difference” capability of your source control to look at all the lines that were changed – which makes it faster to find the source of the error.

Leave a Reply

Your email address will not be published. Required fields are marked *