Re: Subversion and RPG source change

Arco Simonse wrote:

I agree that from an i point of view there needs to be some Master Copy
stored in an i library. But in my thought - and I believe that is also the
Subversion idea - this master copy should always be an SVN working copy,
which is checked out from the repository from a tagged release. Not every
repository revision should be synchronised immediately to this master copy.
Imagine that you have your Master Copy checked out just from a tagged
release, say you tagged it as version 1.24, which is for example at level of
revision number 1540. Another developer has also checked out a working copy
of the trunk to his own IDE, and has worked on some source code. When he
commits this code (maybe in two or three commits 1541,1542,1543) you don't
want to have this code immediately applied to your Master Copy. That would
break a good release management. Instead of doing so, you should look
carefully what the changes in these revisions are, and if it is okay then
for example you will tag revision 1543 as the new production release 1.25.
That is much safer and more conform the Subversion philosophy than let
everybody digging around in your master copy.

I've been reading this thread with a great deal of interest. I do
little development on an iSeries any more, but all of the current Linux
development I do is in a subversion repository. And when I do modify
existing iCode the source gets added to a repository, albeit manually,
just to maintain my sanity.

Just to throw this out there, could you possible leverage the SVN hooks
to update the 'Master' copy held in an iLibrary? I use those to update
tickets in my Request Tracker system but there is no reason that they
couldn't be used in the way you mention.

Barry