Re: Change management systems

[Charles Wilt <charles.wilt@xxxxxxxxx>]

I guess that depends on how good your own tools are.

Big point for me, irregardless of how big your shop is, is the ability
to organize or group changes together in various ways.

Also, when pushing into production, the changes either all go or none
of them do without any manual recovery.

Lastly, now a days CSM tools will offer (optional?) functionality to
support PC & IFS based development, so project that require Java or
.NET client changes can be handled all together.

I suggest getting a demo of the tools, perhaps even a trial.

Given the current economy, you'll probably find a buyer's market.

HTH,
Charles

On Mon, Jun 15, 2009 at 4:22 AM, David FOXWELL<David.FOXWELL@xxxxxxxxx> wrote:
> Lately, had a problem with 2 developpers wanting to modify the same source at the same time.
>
> Never heard of CMS before I was on this list and I'd like to know more about these. We've always had our own installation tools, but constantly finding ways in which they need to be perfected.
>
> What might a good CMS do that our own tools can't?
>
> David FOXWELL
> Service Informatique
> Tél : 03 90 23 91 63
> david.foxwell@xxxxxxxxx<mailto:david.foxwe@xxxxxxxxx>
>
> P Pensez à l'environnement avant d'imprimer ce message
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.