[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CVS - setup reserved checkout
From: |
David Gravereaux |
Subject: |
Re: CVS - setup reserved checkout |
Date: |
Tue, 30 Oct 2001 00:30:53 GMT |
address@hidden (Kaz Kylheku) wrote:
>Tell the manager to shed his or her superstitions, and work with
>the facts. The facts are:
>
>- Concurrent development works just fine.
>- Your team already likes it.
>- Strict locking does not prevent concurrency, it only reduces
> it to a coarse granularity: coarse enough to interfere with
> productivity, but not coarse enough to eradicate conflicts.
> To eliminate conflicts, you have to lock the entire repository
> so that only one developer at a time can do anything on the
> software base as a whole.
Well said. May I add, Concurrency works best with good communication among the
developers. Responsibility of certain sections of code is usually divvied among
just a few people. Strict locking might hurt the need for good communication
among a group.
--
David Gravereaux <address@hidden>
$ make war
make: *** No rule to make target `war'. Stop. Try `love' instead.
- Re: CVS - setup reserved checkout, yap_noel, 2001/10/10
- Re: CVS - setup reserved checkout, Bryon Lape, 2001/10/11
- Re: CVS - setup reserved checkout, Bryon Lape, 2001/10/11
- Re: CVS - setup reserved checkout, yap_noel, 2001/10/11
- Re: CVS - setup reserved checkout, Bryon Lape, 2001/10/11