What paths within the DeployStudio components would be useful to keep track of changes in?
DeployStudio's mpkg is a bundle-style distribution package that contains several packages. All the various shell scripts and configuration files seem to exist within the DeployStudio Admin app bundle at:
DeployStudioServer_vX.Y.Z.mpkg/Contents/Packages/deploystudioAdmin.pkg
Here are several useful top-level paths that could be useful to track:
Contains the sys_builder script and its components used to build NBIs. Frequently updated for fix NBI-related issues.
Source of scripts used for all DeployStudio workflow tasks.
Some other core components shared between Admin and Runtime.
Without any kind of file type filtering these will include things like image resources, etc. but these are unlikely to change frequently and so will not clutter up diffs too significantly. We'd be sure that we wouldn't accidentally filter out files that would be useful to see changes (or new files created), and while it's certain this would also include binary files, these could be also be useful to have at hand for comparison.
Are there any other paths we should track?
Including their release notes somehow would be useful - like you did in the commit message - but I only want to do it if it can be automated, and currently this would be probably best done by parsing the XML feed, matching the NB string to the version downloaded, etc. This is enough work that I'd rather not do in Bash. So, doable, but wouldn't be high on my priority list, but if someone were willing to provide code for that in Python I might consider porting the script to Python.