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

At least David doesn't apply the MKS filter to the Midrange site :-)

Correct that the SVN approach that we are talking about is purely for
source code control. SVN doesn't address the issues or change
management, object management, help desk ticket tracking etc that
commercial solutions provide.

Our main requirement is good "source code version control".

Regards,
Richard Schoen
RJS Software Systems Inc.
"Get the information you need. Now!"
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 898-3038
Fax: (952) 898-1781
Toll Free: (888) RJSSOFT


-----Original Message-----

----------------------------------------------------------------------

message: 1
date: Fri, 30 Nov 2007 13:53:21 -0600
from: David Gibbs <david@xxxxxxxxxxxx>
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).

--
System i ... for when you can't afford to be out of business