From what I've observed, GMU "migrates out" an object and all of the dependencies. I can see this as being very convenient, but it can also be a little dangerous if the source changes frequently. Is there a way to be explicit about migrations?
If I think of the Gateway in terms of a database, I have objects that I would "script out" and move across databases in my environment. Can I do the same thing with GMU? It would be nice if I could "see" the dependencies of the object that I wish to migrate; however, I'd like the opportunity to "build" my migration so that I can be explicit about what is being moved.
I may be over-thinking it, but I feel like a DEV gateway can be in an unstable state at any point in time. I'd hate to migrate dependencies if they have changed without my knowledge.
I'd be REALLY interested in any thoughts on this.