We are using our CVS repository to hold code for Development, Staging
and Production levels of code. Every file holds a tag that identifies
what stage the code is in D - Development, S - Staging, P - production.
When one initially modifies the file (merges it with what is out on
there), the user tags it for Development. Once it has been tested on
their local environment, the user tags it for Staging. Once the file
(or components) have been tested in the Staging environment, it is
tagged for Production.
When the user needs to update their local workspace, they can "check
out" all the versions tagged as Development, Staging or Production.
One could then checkout all the files associated with the Staging or
Production level and do a build and deploy of that level.
I've been searching in the docs and this listserve to determine if and
how I can do this type of version control under Subversion. Am I able
to do this with Subversion; and if so, how is that accomplished?
While not directly part of this question, the last I have seen about a
Subversion Ant Task in this list serve was a question around 2003. I
would like to be able to control the checkout and deploy of the above
process through an Ant Task. Is an Ant Task available for Subversion;
and could I do what I have in mind.
Our project manager wants to move to Subversion (my thought is if it
ain't broke don't fix it...) but we would like to be able to use the
above version control schema....
Stephen L. McConnell
"If you are not part of the solution, you are part of the problem....
Or maybe a precipitant or colloidal suspension...."
-- Lamar Stephens
=====
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 28 00:09:18 2004