Forget abut what you learned in CVS when it comes to tagging (and maybe
branching).
They do NOT work the same way in Subversion. For example, one can NOT
just "move"
a tag.
On 10/9/06, Tanoor Dieng <newstanoor@gmail.com> wrote:
Commits and updates are done frequently and we
communicate a lot so that conflicts don't often appear and when they
appear we solve them manually.
When we have decided that a file is stable we tag it
like that:
cvs tag -F STABLE myfile.
When we want to publish a new version, a script will get
a working copy composed by files with 'STABLE' tag.
In this way, we can continue to work on our files while
we are sure that only files with STABLE tag are put in production.
Have you considered having devs checkout working copies from the
trunk, then merge to the STABLE branch when they are done making
changes? This enables a continuous build & test system to have 2
targets: trunk and STABLE, which is very desireable.
Received on Mon Oct 9 16:34:17 2006