Bit of info from my experience...
1) MDS is a source control system. you do not need to use anything else. Production MDS is your versioned source control and changes should be made there by business users. This method works best but the MDS FE can be very slow and is a bit unwieldy.
2) If you are looking at some kind of waterfall release process through environments, MDS is definitely not the best tool for this. We automated the export of packages to apply to other environments and then you end up progressing the data through to Prod. It is clunky and causes lots of headaches.
We have used both ways and now only keep the first one.
If you have master data that is changed by IT (and not business) and the changes are released through environments then it is far simpler to just chuck the data in a table with a soft-delete/history process (or something similar).
Tom, thanks for your input. I am not interested in source-controlling MDS data. As you suggest, that's what MDS does by itself.
It is the models themselves which are of interest. The entities, subscription views, business rules and permissions, to be more specific. How did you automate their deployment?
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.