> We have plenty of MC packages in our product builds (approx. 100) and
> one of the most difficult tasks can be to figure out what has changed
> between two builds. Is there any good solution for this problem which
> doesn't involve going through the packages by hand? (I will note that we
> have configurations for the builds so we do know which versions are in
> which build). What do others do to figure out what has changed?
Just an ugly workaround: when you have a common (and empty) root
package you can select this one to merge and then get a listing of all
the changes in the dependent packages.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch