[Top][All Lists]

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

Re: creating policy

From: mthread
Subject: Re: creating policy
Date: Thu, 13 Sep 2007 11:52:58 -0000
User-agent: G2/1.0

On Sep 13, 7:25 am, Jim Hyslop <address@hidden> wrote:
> Hash: SHA1
> mthread wrote:
> >    We are using CVS for our project and we have established policies
> > for different team members in the project. I would like to give
> > testing team only the permission to export a version(using export
> > command). No other commands should work for them. Kindly help me how
> > do I go about doing this.
> CVS does not allow restrictions based on commands. I am not aware of any
> plug-ins that allow you to do what you want.
> Off the top of my head, some of your choices are:
> 1) use different version management software;
> 2) enforce the policies by imposing strict penalties for anyone who
> disobeys, possibly including firing them if the situation warrants;
> 3) wrap the CVS commands in a script/batch file/customized GUI, and do
> not allow direct access to the CVS executable.
> - --
> Jim Hyslop
> Dreampossible: Better software. Simply.
>                  Consulting * Mentoring * Training in
>     C/C++ * OOD * SW Development & Practices * Version Management
> Version: GnuPG v1.4.2 (MingW32)
> Comment: Using GnuPG with Mozilla -
> iD8DBQFG6J+pLdDyDwyJw+MRAt6uAJ0Stl8SeLbe90cI2ffQ1IBCWA6SRQCaAxtb
> P/yj+s+TmGkS03BzSuA6Jq0=
> =dEj2

  thanx for the reply. But I am curious how so many projects are
handled using CVS. I am sure every project development team must be
implementing the sort of policy we are looking to implement. Hope more
guys give their ideas for this topic.


reply via email to

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