×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
It's good to hear some agreement, Aaron. Subversion is geared around the copy-modify-merge philosophy, which works well for loosely coupled developers. But there's also a place for having exclusive locks on source members. My inclination would be to provide a parameter on the check-out procedure, and enable programmers to specify the type of lock they want, if any.
-Nathan.
----- Original Message ----
From: Aaron Bartell <aaronbartell@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Fri, May 28, 2010 12:54:26 PM
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/
midrange.com
