Yes, I can understand that point..the problem is that is you have modified
an object that has been included in Update2. If you don't run the software
update application, the object from Update2 is not merged with your (prior)
modified object, but replaces it. Promoting something through with OMW does
not merge, but replace the objects in the project. Second, say you have an
object that was modified in dev, but you never moved it to prod, yet it has
been included in the update2. That object will be merged in dev, then
migrated through to production, wiping out the good object in prod (say it
was fixed in either crp or prod itself) with the bad object moved from dev.
There are plenty of objects in dev that have been messed up and checked
back in..they would be merged and then migrated to prod. I think if you are
going to do the omw route of migration, you should copy prod to dev before
you perform the update2, so you are ensured that you have a good copy of CO.
John