Tja Nicklas,
> In CVS I created a tag 'latest_build' and then used to "move" that tag
> to newer versions as they where tested.
>
> I can't seem to find any references to how this would be done in
> subversion.
How about something like this?
1) Use the ~/projname/tags area for regular tags (as described in
documentation) (if needed)
2) maintain one tag call "latest_build" in the ~/projname/tags area as
well.
3) When a new "stable" tag is created, (or when the trunk seems stable
enough or when you have a working copy that seems stable enough, *svn
delete* the old latest_build tag (if any), and then *create a new
one*.
Try e.g
$ cd ~/projname/
$ ls
trunk tags branches
$ svn delete tags/latest_build
$ ls tags
[no latest_build here]
$ svn copy trunk tags/latest_build
$ svn commit
Best Regards
Lycka Till
Hugo Heden
On Wed, 12 May 2004, Nicklas Norling wrote:
> Hi.
>
> I have a question that I haven't been able to find an answer for.
> I'm hoping anyone of you have a solution.
>
> I've got a continuous integration server building code from trunk
> but would also like to setup a more stabile build environment
> based on some more well tested version of the code.
>
> In CVS I created a tag 'latest_build' and then used to "move"
> that tag to newer versions as they where tested.
>
> I can't seem to find any references to how this would be done
> in subversion.
>
> Can it be done? If so, how would I go about. And if it's not possible
> is there a work around?
>
> /Nicke
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 12 12:26:33 2004