K
kbachtold
Guest
Managing and auditing changes in applications is seriously lacking on a large scale. There is no easy way to see what changed in an application from one version to the next when working with a larger team of developers. It would be really awesome if we could have some sort of change management that understood the structure of an application: 1. Be able to generate a report of what changed from one version to the next. 2. Ability to show differences between previous version of a component and new version. 3. Audit the history of a component back to the original version. The best we've been able to do is try parsing the application xml generated and compare it between two updates. However, the number of changes between even two .xml generated on the same server are so large, it's difficult to wade through the noise and make sense of what really changed. For example, even the order of output of components and object definitions is arbitrary and random from one version to the next generated from the same source customer.
Continue reading...
Continue reading...