I’d like to get others’ thoughts on best practices for maintaining package version compatibility with the latest stable Dynamo build.
At Woods Bagot I prefer to keep all users on the latest stable build to reduce risk on projects. Advanced users are welcome to push ahead to daily builds provided it doesn’t interfere with team collaboration.
The latest stable build, along with a recommended core set of packages, is deployed along with current versions of Revit. This means all Revit users, regardless of whether or not they actively use Dynamo, have the same Dynamo “ecosystem.”
Therefore it falls on me, each time a new stable is released, to go through each and every recommended package (16 at this point) and identify the most recent version built to the stable.
Many times this is one or two versions behind the most recent version of the package, as actively developed packages are built toward daily builds not stables.
This isn’t the most arduous task of all time but it feels a bit inefficient. I’m wondering if there’s a better way to manage this.
From a features request standpoint it would be nice to run an auto-update on all packages to either the most recent version or to the most recent version compatible with the currently installed Dynamo build.