info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CVS misc questions


From: Pierre Asselin
Subject: Re: CVS misc questions
Date: Fri, 3 Jun 2005 00:07:19 +0000 (UTC)
User-agent: tin/1.6.2-20030910 ("Pabbay") (UNIX) (NetBSD/2.0 (i386))

Fabio Miranda Hamburger <address@hidden> wrote:

> I have a misc list of CVS questions regarding web development:

> 1. Let's say you have 10 developers uploading files from dreamweaver to a
> apache server (let's assume no testin). If you implement CVS, how can you
> implement CVS in these situation when you have designer and developer
> without unix knowledgement and without shell access ?

I would use TortoiseCVS.  You will probably have to install it on their
computers.  If necessary, write a detailed memo on where to download
the files and what buttons to click to perform the install.

You should also place the first version of your site in CVS yourself.
CVS is very easy to use once everything is set up, but starting something
takes more work, which you don't want to impose on your web developers.


> 2. Where can I find 'best practise' articles about control versioning? how
> to know you reach a milestone? well, in fact, how to define one?, how to
> assign number to the versions with a logic sense? like linux kernel
> versioning

That's a long story, and it may not apply to your web site since
from what you say the files get deployed to a live server without
going through a formal testing stage.  Only you can tell when you've
reached a milestone.  When you do, the simplest thing is to tag the
project so you can return to that state if need be.


> 3. How to deal with binary files when checking out a sandbox against a
> repository_ For examples, images that belongs to the project, binary logs,
> etc. that are inside the sandbox as a part of ther project

Just make sure they get cvs-added as binary files.  With TortoiseCVS,
this means having a good CVSROOT/cvswrappers file on the server.


-- 
pa at panix dot com


reply via email to

[Prev in Thread] Current Thread [Next in Thread]