[p4] Looking for the best starting point
CRuble at ixl.com
CRuble at ixl.com
Mon Jan 24 11:03:46 PST 2000
Our company builds web sites (any type, any size, any platform). At any
time we might have 10 different projects being worked on simultaneously with
10 different developers per project. Developer tools depend on what
platform is being worked on. The culture of the company is one that is open
to change, if that is what you were asking.
In your branching suggestion below, are you saying that all developers
should work on the same branch? It seems that would limit concurrent
development of the same files.
Automated Build system? Where can I find more info on this?
From: Dave Birkhead [mailto:daveb at extensity.com]
Sent: Monday, January 24, 2000 11:52 AM
To: 'CRuble at ixl.com'; perforce-user at perforce.com
Subject: RE: [p4] Looking for the best starting point
This is a good question, but not one with an easy answer.
It depends a lot on the type of business, development tools and culture
of the company.
In my opinion if the company is producing a web site then branching
should be kept to a minimum. I would suggest a development branch, a QA
branch and a Production branch.
If you are producing software for release then the branching should be
more along the lines of releases and possibly products.
In either case I find labeling to be very beneficial.
An automated build system and an integration with your defect tracking
system can be very helpful as well.
Manager of Release Engineering
From: CRuble at ixl.com [mailto:CRuble at ixl.com]
Sent: Monday, January 24, 2000 10:10 AM
To: perforce-user at perforce.com
Subject: [p4] Looking for the best starting point
My goal: Determine the best configuration management scenario for our
company including all processes, then pick the tool that best fits this.
I've used Perforce in the past and Iiked it. We did branching and I thought
we did a good job, but I never really got into labeling and wondered if this
is a good path. I didn't want to just start implementing branching because
that is what I know.
Does anyone know of a good source to begin implementing cm? I'm looking for
all the questions to ask myself about our organization and process before we
determine the best path to take.
Charlie Ruble, QA Manager
perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user