I've tried it both ways and I find that stand alone update packages with
periodic FULL packages is the best and safest way to go.
With OMW working the way it does and us having to check-out / get the
latest code before assembling a package from a FAT client and then building
on the Deployment server, I found that incremental (if I understand how you
are using this term) was too much work. I build update packages for
whatever needs to go for that day (or since the last update package). When
I have a number of these update packages or a significant number of objects
built within them I then build a full package and start the cycle over
again.
I have gone and recompressed the parent package again to incorporate the
update packages into the parent that they are built against but I have run
into problems where an update package contained fixes for one problem but
caused a more serious problem in other areas of the system. If you
recompress the parent package with the update package fixes then you can
corrupt the parent package as well... then how do you back out easily?
Granted there is a backup/restore option for ESU's but not for development
objects your guys create.
Bottom line for me is that I build a Full package, then subsequent update
packages as required with only the objects needed for that update build -
not cumulative - and when I get enough of them I build a new Full package
again. Yes this means that for every new client I install I have to
install the full package and every update to bring the client current, but
if there is a problem with the objects in any update package I can easily
remove it from a client by simply reinstalling the good packages - no
messing with source code until a proper fix is found. Of course having a
small number of Fat clients helps this process too.
I hope this helps.
Regards,
Gerald.
LoriStephens
<jdeperson@hotmai To: Gerald Kastanek/Toronto/IBM@IBMCA
l.com> cc:
Sent by: Subject: Anyone doing cummulative update packages?
owner-jdelist@jde
list.com
04/04/2002 04:37
PM
Please respond to
jdelist
Hi,
I have a request. My first CNC Consultant told me to do cummulative
updates. Now I have another CNC Consultant telling me I shouldn't be doing
them. Question is: Are you doing cummulative updates? Why or Why not?
I realize now there could be a problem in the development pathcode if they
are changing things regularly. But why not do it in the others?
Thank you!
Lori
OW Xe SP16 Update 2
AS400 V5R1 NT
Citrix
email:
[email protected]
--------------------------