Re: CMS vs. SCS

Isn't SCS a basic component of a CMS? Doesn't Eclipse team support allow
for " multi-tiered
environments with things like configuration files, internal databases,
binary files (DLLs, JARs, etc), images, you name it"?

If you need to share, I have found Subversion, Subclipse and Eclipse Team
support to be able to share, for all practical purposes, ANY artifact
required, not just source. And I have found this support to far exceed the
utility of a network hosted workspace. The small cost is setting up a
subversion repository (download Apache web server, Subversion and install
the Subclipse plugin. All free). It is sort of a first step to CMS anyway.

I understand the indescribably profound utility of a CMS. I just strongly
discourage teammates from sharing workspaces.

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of Joe Pluta
Sent: Thursday, February 14, 2008 12:08 PM
To: Websphere Development Studio Client for iSeries
Subject: [WDSCI-L] CMS vs. SCS

Luis Colorado wrote:

Joe,

If you are not a big believer in source control systems like CVS, what do
you believe in? Any recommendations?

For production work, CMS (Change Management Systems) provide much more
functionality than SCS (source control systems).

CMS is indispensable if you have even two programmers in a shop. Heck,
CMS is nice if you can afford it in a one-person shop. It's essential
to be able to relate objects together (display file and program), to
check them out, and to be able to promote both source and object through
phases such as development, QA and production (not to mention being able
to distribute them to other machines in larger environments).

It's even more of an issue when you start talking about multi-tiered
environments with things like configuration files, internal databases,
binary files (DLLs, JARs, etc), images, you name it. And really good
systems provide hooks to things like incident reporting and bug
tracking, and even project management.

Most source control systems are about allowing multiple people to write
code. CMS systems are for managing application development and
distribution.

<snip>

Joe