On 6/5/06, Steven Lavallee <stvcinlav@yahoo.com> wrote:
>
> I am a new user to Subversion.
>
> 1. Can we migrate code to our QA and Production
> environments but tagging the specific code changes?
>
> 2. Would we use branches to migrate the code after it
> has been approved?
>
> We have DEV, UAT, QA and Production environments and
> we want the ability to migrate just the specific code
> changes not the entire source code.
Before going too far, understand that unlike with CVS and other SCM
systems, branches (and tags) carry no special significance in SVN -
they are just copies. SVN can't tell the difference between a tag,
branch, or copy (they're all just cheap copies)
Answering your questions:
1) Most users will tag a full release, not specific files/changes.
Basically taking a snapshot of the whole source tree at a moment in
time. The idea being the ability to point at a URL and say "if you
look here, you will always find release 1.4.62."
2) A common use case is to create a branch from trunk to use as the
basis for QA and testing. Create a branch called "version_1.0.0" and
then any changes required as a result of QA are made here and ported
to trunk later. Once QA has signed off, you'll probably create a tag
from here indicating the final 1.0.0 release.
If you haven't yet, The Book (http://svnbook.org/) is a very
worthwhile read and can help answer a lot of questions. There are a
few others that have been very helpful to me as well; /Subversion
Version Control/ by William Nagel (he participates on this list as
well), and /Pragmatic Version Control Using Subversion/ by Mike Mason.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jun 5 22:38:26 2006