Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Possible Duplicate:
How to use SVN, Branch? Tag? Trunk?
I have seen several articles that describe the best svn layout to be:
Why is this the recommended layout and what exactly are the Branch and Tags folders supposed to be used for?
/Trunk is the base folder of your application’s code. It is here that you do work on your next version / release.
/Branch is a folder that allows you to pick a moment in time and allows you to go down a different path of development than that of /Trunk. A common use of /Branch is to provide your development team with access to a current snapshot of your application as it exists in production, ie. /Branch/production-maintenance.
This ‘branching’ concept allows your team to build fixes/enhancements to production, without affecting the ongoing work for your next version, currently happening in /Trunk. Branches can also be mini-pieces of functionality that, in large teams, allow developers to work on atomically, and merge back into /Trunk at a point in the future.
/Tags is a folder that allows you to take snapshots of your application, and work with just those particular “builds”. This allows your team flexibility, both in testing, and in finding the differences between builds. You will often find a naming convention followed in /Branch, which relates to your builds, ie. /Branch/2.0.0, /Branch/2.0.1, /Branch/3.1.0, and so on. The naming convention is up to you and your team; keep it consistent!