Re: Locking CVS

[S I]

All 3 projects are under /usr/local/cvs/proj1 thru 3.  I just added a blank 
writers file.  Will this do it until I do a final build, tag, and branch?

----Original Message Follows----
From: Todd Denniston <address@hidden>
To: S I <address@hidden>
CC: address@hidden
Subject: Re: Locking CVS
Date: Mon, 11 Jul 2005 11:01:21 -0500
MIME-Version: 1.0
Received: from mail.ssa.crane.navy.mil ([164.227.42.3]) by 
mc1-f12.hotmail.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 11 Jul 2005 
09:04:32 -0700
Received: from ssa.crane.navy.mil (address@hidden 
[164.227.42.142]) by mail.ssa.crane.navy.mil  with ESMTP id LAA19518; Mon, 
11 Jul 2005 11:03:05 -0500
X-Message-Info: JGTYoYF78jEHjJx36Oi8+Z3TmmkSEdPtfpLB7P/ybN8=
Organization: Code 6067, NSWC Crane
X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.2.25glock1 i686)
X-Accept-Language: en
References: <address@hidden>
Return-Path: address@hidden
X-OriginalArrivalTime: 11 Jul 2005 16:04:32.0380 (UTC) 
FILETIME=[39A923C0:01C58632]

S I wrote:
>
> Hi everyone,
>
> I'm planning to lock cvs today getting ready for our release.  I realize
> with certain version control software nowadays you don't have to lock the
> repo and the developers can continue with their work.  However, we're
> imposing and enforcing a few days for freeze and to regroup.

Another method would be to tag and then branch, decide whether the trunk or
branch is where you will host the release, and use cvs_acls to lock down the
trunk/branch for release work only. look at ACME [2] for ideas.

>
> Our repository resides on a linux box with :pserver method access from 
WinXP
> CVS DOS and Tortoise clients.  Could I just lock the repo by executing 
cvs
> admin -l or -L  or do I have to download some perl module to accomplish
> this? I need to lock our CVS repository today.  Three projects reside in 
the
> repository, is it possible to lock them selectively or would admin -l 
lock
> the entire repo?
>

There are  a few ways I think you could go at it.

If you don't even want anyone reading from the repo, you could temporarily
remove it's allow-root option from [x]inetd.conf.(assumes the three projects
have different roots in [x]inetd.conf)

if you are ONLY accessing the repo via pserver, the reader / writer [1]
files could do it for you.(assumes the three projects have different roots
in [x]inetd.conf, OR that none of the developers work on multiple projects)

if you want fine grain control, look at using cvs_acl, from the distribution
contrib directory, as a commitinfo script.

[1] https://www.cvshome.org/docs/manual/cvs-1.11.20/cvs_2.html#SEC36

[2] http://www.cmcrossroads.com/bradapp/acme/
    http://www.cmcrossroads.com/bradapp/acme/branching/

--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter