[Top][All Lists]

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

Re: Tag locking change

From: Greg A. Woods
Subject: Re: Tag locking change
Date: Wed, 9 Oct 2002 13:58:36 -0400 (EDT)

[ On , October 9, 2002 at 10:03:08 (-0400), Adam Bregenzer wrote: ]
> Subject: Re: Tag locking change
> I can think of specific examples where testing, etc. may not happen in a
> 'working copy' of the code.  For example, one of the projects I am using
> cvs for is a website.  I have a script in cvs that, upon checkin, copies
> the file over to a directory so that the 'current' cvs version of the
> site can be immediately tested.

Yes, sure, but that copying is done (or at least the source for the
copying is created with) "cvs update", RIGHT?  (i.e. it had better be!)

>  There is not branching in the code or
> anything fancy so I currently use rtag to tag the head of the branch
> when we decide it is ready.

When it's "ready" you should be "cvs tag"ing the working directory which
matches the "ready" revisions of the files.

What do you do with that tag afterwards?  Presumably you "cvs export"
using it and create a master copy of the "ready" files to ship to your
production web servers?  That would be the right way to do the release.

> Also, it can be convienent to use
> rtag if cvs is integrated with other tools.

You mean to tag the head of a branch?  That doesn't make sense.  What's
more "convenient" about getting undefined results!?!?!?!

                                                                Greg A. Woods

+1 416 218-0098;            <address@hidden>;           <address@hidden>
Planix, Inc. <address@hidden>; VE3TCP; Secrets of the Weird <address@hidden>

reply via email to

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