Hi,
Carlos Costa Portela wrote:
> Here at demasiado.com, we're using cvs to help us develop our
> website. In a development cycle of a program (traditional development
> cycle) is it ok have two versions: one stable and other unstable. Our idea
> is to only touch the stable version to correct bugs found in the current
> on-line verision.
>
> We make two types of changes: simple ones (bugs and simple text
> changes) and others more complex (new apps in development). In our
> situation we feel we cannot use cvs in the classical way.
>
> We're really not sure how to make this work well, so if you could
> help point us in the right direction, we'd greatly appreciate it.
Chapter 5 of CVS-manual describes the handling of such a szenario:
You are working on a main trunk. If you release a new version, then you
tag it (and check out this version to your Webdocs-Area). Further
development is done on the main trunk. If you have to change something
of the stable release, then you branch from this stable release and fix
the "bug". After that, you can include this fix into main trunk (if you
want to). Then you update the checked out version in your
Webdocs-directory.
I think that's what you wanted to do, is it?
I'm doing it here to, maintaining a db-based Web-application.
If you are working with apache as web server, then you should configure
it to exclude CVS from documents, e.g.
"IndexIgnore .??* *~ *# HEADER HEADER.html README README.html RCS CVS"
As I told you, it's well described in the manual.
Ciao for now, Dirk
--
Dirk Ruediger, Rostock, Germany
Leben l�sst sich nur r�ckw�rts verstehen, muss aber vorw�rts gelebt werden.
Soren Kierkegaard
