Hi

I know that those with strong opinions love Perforce but you should
also look at subversion or SVN

This is an extremely well used open source CVS and works in a similar
way to perforce. But, what sold it for me, was that it is free and you
can buy several textbooks on using it from Amazon.

If you are developing at the jBase shell using JED then you have to
consider one direction and if you are using some sort of gui
development environment, you can go a different way. With winbdows you
can use Tortoise (also free) to manage the repository and what you are
doing, or the KDE version or you can build command line tools from
Basic to execute the svn commands - which is just what I did and do.

If everybods is using the same development server then the logic still
applies.

Each user checks out a copy of the part of the repository that they
want to work on (careful thinking about how you want to manage the
repository reduces the incidence of send terabytes around the
network). The user checks out a working copy. Updates what needs to be
updated and checks their working copy back in. If someone else has, in
the meantime, also changed the code then you cannot commit and you get
error message(s) to tell you what the problme is. Do some sort of diff
on the 2 copies of the source code, fix the issue and commit and your
done.

It is much easier if you develop in winblows because the diff tools
are much nicer but that is all and you may never need it. In 12 months
and 10 developers, we never got the wires crossed so that we had to
use diff to fix a change.

Just my 2c

MIke

-- 
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

Reply via email to