RE: Source Code management - Migrating packages

You have the ability to compare the source for both.

I tend to think that two developers shouldn't be working on the same
program in the first place, however if someone is sitting on the program
for a while, I would take the production version of the code for the new
request versus that which has not been promoted.

Issues I have seen have mostly been with developers. Compiling logicals
over existing files in development without going through Implementer,
backup copies of programs, etc.

When I was promoted into my current position, I inherited the
Implementer setup.

It really does work like a charm & "prohibits" developers from hosing up
production.


Thanks.
James Salter
Systems Programmer
American Cast Iron Pipe Company
phone (205) 325-3033
fax (205) 307-3833


date: Wed, 27 May 2009 12:22:26 -0600
from: "Dan Kimmel" <dkimmel@xxxxxxxxxxxxxxx>
subject: RE: Source Code management - Migrating packages


Does MKS do a decent job of merging changes from two (or more)
developers?
_________Confidentiality Notice_______________________
This e-mail and any files transmitted with it is
confidential and is intended solely for the use of
the individual(s) or entity(ies) to whom this e-mail
is addressed. If you are not the intended recipient
or the person responsible for delivering the e-mail
to the intended recipient, be advised that you have
received this e-mail in error, and that any use,
disclosure, dissemination, forwarding, printing,
retention or copying of this e-mail is strictly
prohibited. If you have received this e-mail in
error, please immediately return this e-mail to
the sender and delete the e-mail from your system.
Thank you.