RE: Subversion and RPG source change management

["Dan Kimmel" <dkimmel@xxxxxxxxxxxxxxx>]

This assumes you have one working copy in IFS and checkout/checkin to
SEU from that one working copy. That negates some of the benefit of SVN.
What you want is a one-to-one between IFS working copy and source
library for SEU. You can have as many working copies as you want at the
same or different revisions. You want to have the same number of
libraries, each tied to one working copy in the IFS. Then you don't need
any exclusive checkout system. 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Aaron Bartell
Sent: Friday, May 28, 2010 1:54 PM
To: Midrange Systems Technical Discussion
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/


On Fri, May 28, 2010 at 11:48 AM, Nathan Andelin <nandelin@xxxxxxxxx>
wrote:

> > From: Mark Murphy
> > Unfortunately the Commit can fail if there are conflicts, and needs 
> > to be watched.
>
> That's true, but I don't have a problem with it.  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.
> If a nightly commit fails, just send the programmer an SMS or email 
> message, and add a record to a history table.
>
> -Nathan.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.