Re: Subversion & iSeries

Adam Glauser wrote:

I can't say that SVN has _never_ been used (abused?) as a change
management tool, but I can't imagine that it is common practice to do
so. As Charles mentioned, Unix/Windows people normally use a
combination of tools (make/ant + SVN/CVS + unit testing tool) to provide
CM functionality.

I concur on that ... SCM is a lot more than just source management.

I'd suggest researching make, ant and COMPILE before taking the plunge.
They may well do enough for your needs.

That configuration might work well in a very small, controlled,
development environment ... but if you're environment gets even a little
bit big those tools will quickly become cumbersome due to the fact that
you have to manage all the build parameters yourself.

A good SCM product will offer the ability to retain compile attributes
for objects so you don't have to manage them yourself. Plus there's the
whole issue of data retention when you change a physical file (which is
a trick in the best of cases). Additionally, most SCM products offer
some kind of work flow capability so that changes happen in the correct
sequence and by the appropriate people.

david
(who, in the interest of full disclosure, does work for MKS ... a SCM
vendor ... in addition to running midrange.com).