2 messages in com.perforce.perforce-userStrategies for roll-out| From | Sent On | Attachments |
|---|---|---|
| Will...@intuit.com | 24 Jul 1998 15:59 | |
| Davi...@home.chat.net | 25 Jul 1998 00:38 |
| Subject: | Strategies for roll-out |
|---|---|
| From: | Davi...@home.chat.net (Davi...@home.chat.net) |
| Date: | 07/25/1998 12:38:57 AM |
| List: | com.perforce.perforce-user |
On Fri, Jul 24, 1998 at 03:59:30PM -0700, William Africa wrote:
I was wondering if anyone could advise my on strategies of how to roll out Perforce over an existing source control system. I would appreciate techniques on how to do PR work to an engineering group. In other words, how can I "sell" Perforce as a product that could move our engineering efforts forward? Also, what types of plans can be used to migrate users over with as little as pain as possible?
The best way to 'sell' any product internally is to:
1) enumerate your current goals 2) assess whether or not your current system meets those goals 3) enumerate future goals 4) assess whether or not your current system can meet those goals 5) if the answer to either 2 or 4 are either 'no' or 'not without lots of work', then look at how other products meet those goals
I've come up with few orginizations to compare the existing source control systems. One places them on a 'file revision' <-> 'configuration management' scale.
1. File revision tools:
RCS, SCCS
2. tools which provide a nicer UI to store and access single file revision data for groups of files (i.e. projects):
PVCS, SourceSafe, CVS
3. tools which store revisions in a project oriented manner, and which can relate changes
Perforce, ClearCase
Another metric which is important is whether or not they are truly client server. In itself this isn't important (because it's featureset and reliability which is most important). However, there is a strong correlation here between client/server orginization and speed and reliability.
non-client server:
RCS, SCCS : make no attempt to arbitrate multiple users (other than single file locking)
PVCS, SourceSafe, CVS : make some attempt to arbitrate multiple users, but side-effects as benign as non-correlation of data, and as serious as database corruption may occur because clients directly access files. (i.e. multiple simultaneous changes, or client crashes)
client-server
Perforce, ClearCase : control access to the server datafiles. Only the server touches them. All clients make requests against the server.
--- David Jeske (N9LCA) + http://www.chat.net/~jeske/ + jeske at chat.net