The subversion code structure is organized as follows:
<workarea> ---- trunk
---- branches
---- releases
---- tags
- The trunk is the latest development version and can expected to be unstable at times.
- The branches path is used to create special (or temporary) branches. For example, if a developer is working on some new experimental feature then (s)he would create a temporary branch, complete all development and then merge it back to the trunk path.
- We use the releases path to maintain a branch of the major versions- for ex. 0.8, 0.9.8, 1.0, etc.,
- The tags are just a pointer to the different revisions which were used for the application that was released out to the opensource. For example, 1.0 alpha was released out on 26th May 2007. So the tags/1.0 has a directory called alpha_1.0_25may2007. In this directory there is one text file which indicates that the release was made using R753 and the release url was https://svn.openqa.org/svn/wet/releases/1.0/