Hi
I'm looking of migrating our source control from our own home grown
system to a "proper" SCM.
I'm looking at Perforce, as it's the one Jim always advises I should
use... It supports a command line API as well as working with Visual
Studio as a plug-in for our dotnet software.
I'm looking at the command line interface and thinking of the best way
of implementing. Currently, we have a single centralised server where
we directly edit our databasic code. We only have 3 developers. We
don't use check-in/check-out currently - and the process of making
software releases is much more informal - "Are all code changes
complete". We have been lucky, as this has always worked well.
I'm looking for some advice as to how to best implement P4 into this
environment. It looks like I can build a simple source code control
"shell" around the P4 CLI commands to check in/check out code from the
Perforce system. However, I'm not sure how we can then make software
revisions - I presume we do this from the Perforce repository..
As you can probably see, I'm confused. I've read some of the html
online guides for Perforce but there are some assumptions are made that
the user knows about source control systems.
I seem to think that Perforce almost assumes that every user has their
own full copy of the softwar environment (ie a local copy of jBase and
all the source code) and then checks out the code they want to edit from
the Perforce server, checking it back in when complete. Is this
correct? Do I presume therefore that regularly, all checked-in code
needs to be distributed to all development servers ???
Am I even close on how this would work ?
Can anybody clarify?
Thanks in advance
Simon
--
Please read the posting guidelines at:
http://groups.google.com/group/jBASE/web/Posting%20Guidelines
IMPORTANT: Type T24: at the start of the subject line for questions specific to
Globus/T24
To post, send email to [email protected]
To unsubscribe, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
