22
My team recently decided not to use the "trunk" branch that is typical of most subversion repository layouts. We found that at any given moment there was always a particular branch that functioned in the traditional role that trunk would hold in other repositories. That is, we always have a highest-numbered branch that represents the next release that we are working on. Therefore a merge to trunk is simply superfluous, so we got rid of trunk.
Does anyone else out there do this?
If so, have you noticed any pros/cons?
Even if your team does not do this, does anyone have any thoughts on this layout?