Git vs. SVN version control systems
With all version control systems, project files sit on a server that you push your files to when you have completed your work on your local machine. However, deciding whether to use a centralized version control system (like SVN) or a distributed version control system (like Git) will affect how you commit changes.
Remember, not all version control systems fit all teams and all needs. A method that works perfectly for one company may be entirely wrong for your team. To determine which system to use, you need to look at how each system works.
What is SVN?
Apache Subversion, also known as Subversion, SVN represents the most popular centralized version control system on the market. With a centralized system, all files and historical data are stored on a central server. Developers can commit their changes directly to that central server repository.
Work is comprised of three parts:
1) Trunk: The trunk is the hub of your current, stable code and product. It only includes tested, unbroken code. This acts as a base where all changes are made from.
2) Branches: Here is where you house new code and features. Using a copy of the trunk code, team members conduct research and development in the branch. Doing so allows each team member to work on the enhanced features without disrupting each other’s progress.
3) Tags: Consider tags a duplicate of a branch at a given point in time. Tags aren’t used during development, but rather during deployment after the branch’s code is finished. Marking your code with tags makes it easy to review and, if necessary, revert your code.