Re: Subversion and RPG source change management

I don't believe the SVN checkout locks anything does it ?

Each user gets a sandbox working copy.

Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business
Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
------------------------------

message: 6
date: Fri, 28 May 2010 13:54:26 -0500
from: Aaron Bartell<aaronbartell@xxxxxxxxx>
subject: Re: Subversion and RPG source change management

It's quite probable that commit conflict resolution would have to be

performed asynchronously, anyway; perhaps phone contact with the other
programmer who committed his changes first; source compare; source
merge;
resolve differences.

I think this is where a "check out" system coupled with a nightly mass
commit from SEU to SVN would be perfect. By checking out a source
member
you lock others from modifying the same one until you check it back in.
And
since there is only one person modifying it you shouldn't ever need
merges -
or at least it would be rare.

Aaron Bartell
http://mowyourlawn.com
http://mowyourlawn.com/blog/