EP18 – Using SVN #likeaboss
This week Arlo and Ryan discuss what you need to know if you want to use SVN as your version control system.
Download: Direct Link
Itunes: itunes link
Hack of The Week
Ryan talks about Doctrine 2 on how it could be used in your current PHP project.
What is SVN?
- General Concepts
- Type of file versioning.
- Revision control.
- True atomic operations.
- Open source.
- File logging.
- History
- Was preceded by CVS: Concurrent Version System -> 1986, still mostly compatible.
- Born in 2000 by CollabNet.
- In 2001 it was hosting itself.
- Was around before git was born in 2005.
- In 2009 , it became an Apache Foundation Top level Project.
- Subversion manages at least 60-70% of development code.
- How is SVN different from git
- Centralized source code control.
- merging hell
Basics of SVN
- Principles
- Collections of files are called repositories.
- Repositories have a directory structure.
- SVN works on changes, not on files.
- These are called changesets
- Two revisions make up a changeset.
- changeset can make a patch
- Commands
- checkout (BIG)
- add (BIG)
- commit (BIG)
- update (BIG)
- status
- diff
- merge
- export
- mv
- cp
- revert
- resolve
- resolved
Online services
- springloops
- They do have a free plan.
- Support SVN, as well as git.
- Other AWESOME tools like deployments, and tickets, etc..
- Closed source
- 2 users, 1 repo.
- GoogleCode
- Free
- Open source only
- Also does project management, ticket tracking, etc…
- SourceForge
- Free
- Open source only
- Also does project management.
- Good end-to-end solution for open source projects.
- Codesion
- Free
- Closed source
- Only 1 user.
- Beanstalk
- Free Trial
- One user, one repo.

