How many users? Multiple Depots? - Dave...@cccpp.com - com.perforce.perforce-user

17 messages in com.perforce.perforce-userHow many users? Multiple Depots?

From	Sent On	Attachments
EdMa...@wrq.com	14 Aug 1998 09:16
Mark...@tus.ssi1.COM	14 Aug 1998 09:45
Dave...@cccpp.com	14 Aug 1998 10:00
WesP...@softweyr.com	14 Aug 1998 10:24
Jack...@alamar-usa.com	14 Aug 1998 10:40
Scot...@seanet.com	14 Aug 1998 10:47
Rich...@netapp.com	14 Aug 1998 10:53
Mark...@tus.ssi1.COM	14 Aug 1998 10:57
Scot...@seanet.com	14 Aug 1998 11:14
Rich...@netapp.com	14 Aug 1998 11:16
Dave...@vignette.com	14 Aug 1998 11:43
Scot...@seanet.com	14 Aug 1998 11:44
Davi...@home.chat.net	14 Aug 1998 11:45
Rich...@netapp.com	14 Aug 1998 11:51
chri...@natinst.comchris.bartz	14 Aug 1998 12:24
SamF...@channelpoint.com	14 Aug 1998 13:21
WesP...@softweyr.com	14 Aug 1998 13:39

Subject:	How many users? Multiple Depots?
From:	Dave...@cccpp.com (Dave...@cccpp.com)
Date:	08/14/1998 10:00:32 AM
List:	com.perforce.perforce-user

We have many projects under a single depot. Under the depot, we have "folders"
for things like tool, documents, sites, home, etc. Under each of these, we have
numerous subprojects in use by many people (locally and remote).

We manage/limit access via client mappings and the 'p4 protect' command. It
works well.

I don't know why you would need to archive "old" projects in separate depots.
Perforce *is* an archive in that it has all your old versions. You can get the
old versions by syncing to a label or changelist. If you don't want the old
versions to be seen, you can fix that with client mapping or even 'p4 delete'
(which doesn't delete the earlier versions). You can also "copy" them with 'p4
integrate' if you want to freeze a certain version.

- -dave

------Original Message----- From: Mark.Blair at tus.ssi1.COM [SMTP:Mark.Blair at tus.ssi1.COM] Sent: Friday, August 14, 1998 9:46 AM To: Perforce-list Subject: Re: How many users? Multiple Depots?

Ed Mack <edm at wrq.com> wrote:

2. Though Tech. Note #20 describes that, at Perforce, they use a single server for development, it does not divulge whether or not they use more than one depot on that server. We are about to set up two distinct product teams (about 20 users on each team) on a single Perforce server. Is there any reason to *not* create a separate depot for each team on the same server? We use full depot-syntax anyway, so nothing would change here.

I'd like to take this a step further. I'm currently evaluating Perforce as a possible replacement for the revision control system my group currently uses. If we choose to go with Perforce, I think I would like to place each project in a separate depot, so that it would be simpler to archive old projects and then restore them later if necessary. Thus, we would have maybe up to 10 or 20 depots on the server at any given time. Would that be a problem? Is there a practical limit to the number of depots that can exist before things bog down or become unreliable?

Any advice would be appreciated.