On Tue, 15 May 2007, James Wood wrote:
> I'm fairly new to the SVN world but am having a great time with it.
>
> I have set up my repository as suggested
>
> trunk
> tags
> branches
>
> Currently our main development is taking place in the trunk and we have a
> stable tag that the live servers are pointing to. No we have a "hot fix"
> that needs to be implemented, but I can't just create a new tag as there is
> code in the trunk that hasn't been approved for general release yet. I was
> hoping that I could just do an update to the tag for the 1 file that needs
> updating but I don't think that is possible.
>
> Can anyone please point me in the correct direction as to how to accomplish
> what I am trying to do.
>
> Also if there are any recommendations as to how I should be using the
> repository to prevent such problems that would be great. Should I be
> developing on a branch?
First off is that subversion doesn't care if you modify the tag,
it doesn't know that it is "supposed to be" read-only. I'd either modify
the tag, or else copy the tag to a branch, and then modify it there, and
then make a new tag.
The way I use subversion is that the trunk is pretty unstable, and
we work there until we get reasonably close to a release, and then almost
everyone "svn switch"es to the branch, and continues. Then we tag each
minor release, and continue in the same branch. So, we currently have:
1.3 is the trunk, and has an unknown release date, and probably compiles,
but there are probably GUI errors that no one has gotten around to fixing.
1.2 is our active branch
and recent tags are 1.2.0, 1.2.1, and 1.2.2 is coming out shortly.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Tue May 15 20:04:59 2007