Re: Shouldn't WDSC include SCM? was: Automate source code backup to SVN

To add to this - source control-only tools do nothing about implications of change - when you alter a PF, you have lots of dependent objects to deal with. Java does not have this issue, nor do most other languages and all. The object-based nature and dependencies on the iSeries are one of our great benefits, as well as one of our great problems to deal with.

SVN and SourceGear and the like know nothing of these things.

Another matter that these tools DO look out for is conflicts between developers working on the same source - that is a great benefit.

I think the new kid on the block-ArCad-claims to use ant for build scripts. It also claims to handle source and change for objects on disparate platforms - it remains to be seen if that is the case. ILE objects have given both ACMS and TurnOver fits - i've never looked at Implementer (sorry, David) so don't know how it handles cross-platform stuff - the holy grail I know I've wanted for at least a decade.

Source control is a far cry from change management - and might be adequate for non-iSeries development. Also, in a 1-person shop, maybe that's enough for iSeries work. Still, changes need to be propagated correctly in the iSeries.

Getting off my soapbox now!!

Back to my vacation!
Vern

At 01:58 PM 11/30/2007, you wrote:

Very true David. I like it when something tracks it when someone ran a
CHGPRTF to change an overlay or something, and integrates the change with
my new revision.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





David Gibbs <david@xxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
11/30/2007 02:54 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
Re: Shouldn't WDSC include SCM? was: Automate source code backup to SVN






rob@xxxxxxxxx wrote:
> There's a lot of SCM vendors out there that are glad that WDSC does not
> "include" it.

Very true <grin/>.

Another thing to consider ... change control, on the System i, isn't
just about managing source code. And it can't be restricted to just
WDSC usage.

Change control also includes managing the objects that are generated by
the source (and the non-source results of combining multiple objects).
There are attributes that need to be retained, data in files that can't
be discarded, etc.

Plus you've got all the SEU users who don't want to (or can't) use WDSC.
A change control solution needs to accommodate those users too.

david
(who, as most people know, works for MKS ... a change control vendor ...
in addition to running these lists).