Don Hoover wrote:
> First off, this might sound a little different because
> we use version control for managing unix system
> configuration files not application source code.
...
> My Question is in CVS, we used tags to keep track of
> what files were "ready to be pushed out" and which
> ones were still being worked on.
>
> Basically, as a file was "ready" to be pushed out to
> all the systems it would be tagged as "PRODUCTION"..
> and only files with that tag would be checked out by
> the automated system for distributing out to the
> systems every day.
>
> This lets the system admins work on stuff and get
> stuff setup, like say a new database config or
> something and only when they are totally ready does it
> get promoted to "PRODUCTION" and pushed out.
>
> Basically we have a tag called PRODUCTION which we
> periodically might update with a new file or maybe a
> newer version of the file but have them all with the
> same TAG name.
Seems like it would work well for you to:
* Develop new stuff on one branch (trunk?)
* "svn cp" it into "branches/PRODUCTION" when ready
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 26 19:58:19 2004