branch - svn branching and tagging best practices -
I have a project for which I am ready to create a branch, which will be 1.0.x for all 1.0 . .x Changes I have to do a set of tags according to changes made in that branch, i.e. 1.0.1, 1.0.2 etc. When I am creating 1.0.x branch for the first time, I am also making a tag called 1.0. At this point, the branch and the tag have the same content (as I had changed the 1.0.x branch, I would create new tags for 1.0.1, 1.0.2 as described above). It seems that the way svn stores a bit of duplication with the branches and tags is it a good practice to make branches and tags? Or is there a better way to do this?
Thanks, Jeff
svn really does not care how projects are stored , Truck, tag, branch layout is just a suggestion. It seems that you are going to use your branch for the development of the main branch, and then for tagging the branch to be posted as a version, it seems to me that traditionally used in the trunk Brunch is done. Here's a pretty standard development cycle:
Building new features -> Prevent new features, Stabilize trunk -> Tag version -> Creating new features in trunk (
is exaggerated, but this is a good starting point.
Comments
Post a Comment