Re: Subversion and RPG source change management

Hi Dan,

The vast majority of IBM i development is on a centralized server, by tightly-coupled development teams, and subject to some structure.

Having a check-out & check-in mechanism against IBM i source members, which enables optional exclusive locks; but paired with an eventual reconciliation with a Subversion repository, seems like a fitting compromise between the draconian measures that some shops implement while endeavoring to comply with SOX, verses a world-wide open-source development structure, where anyone can take the code base in just about any direction they might desire, without limitations.

It also addresses any performance concerns, which bears repeating. Check-out, change, test, check-in; all very quickly and efficiently. Let the synchronization with Subversion be performed asynchronously. Then handle conflicts, when they arise, which in most shops would be rare.

-Nathan.





----- Original Message ----
From: Dan Kimmel <dkimmel@xxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Fri, May 28, 2010 3:11:19 PM
Subject: RE: Subversion and RPG source change management

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.