We are using cvs in somewhat of a non-standard way.
We have a production cut of our compiled source that
we deploy via cvs using a production branch. The
application does not mind the fact the CVS control
files co-exist within the source and the application
runs fine. When we want to patch production we first
patch the same branch in a different checkout area and
then commit it. When it comes time to upgrade the
production area we bring down the application during a
maintenance window and perform a cvs update in the
production area. This has worked great for more than a
year so I am very happy with this process. We were
basically mimicking this process in a pre-production area
for QA purposes and while this has worked OK we are
having a bit of trouble keeping these two branches in
sync. So, I know that I can remove a branch via the
cvs admin -n command and I am wondering if a better
process would be to remove the preprod branch every time
I move a new patch to production and when it comes time
to test the next patch just recreate the preprod branch
off of the current prod branch. I have performed some
tests using this method and all seems to work fine but
I thought that I would ask the opinion of those who have
been using CVS a lot longer than I.
Thank you for your time,
Don Butts
_______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
