Menu
I have a mixture of small and large projects in SVN. Some of them are so small I can't ever foresee myself branching or tagging.
So, should I still stick with the trunk/branch/tag folder convention even if I'm fairly certain the branch/tag directories will go unused for the smaller projects? I just feel like it might be overkill.
Thoughts on this?
580
A tag is just a marker. Trunk would be the main body of development, originating from the start of the project until the present. Branch will be a copy of code derived from a certain point in the trunk that is used for applying major changes to the code while preserving the integrity of the code in the trunk.
Using the trunk and branches In smaller software projects, the trunk folder usually contains the most current version of the project's files. Most people in the team will just have a working copy of the trunk stored on their own computers and do all of their work in there.
All you need to do is make a copy of your project using "svn copy". This command will require the URL of your project's /trunk directory as well as the URL of the directory where you want to create your branch. This location will virtually always be inside of your /branches directory.
- A trunk in SVN is main development area, where major development happens. - A branch in SVN is sub development area where parallel development on different functionalities happens. After completion of a functionality, a branch is usually merged back into trunk.
To answer the question in your title directly: no, you don't have to. SVN repositories can be organized in any folder structure you choose.
That being said, it's probably a good idea to at least put everything in a trunk folder for now, so that if later on you change your mind and decide that branching or tagging would be useful, you can add branch/tag folders easily, without having to move everything around.
165
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
