Search the Community
Showing results for tags 'version'.
-
For keeping track of used packages for our projects we'd like to put a list of used packages to our measuring data. That way we could later on see if a specific problem we encounter with our measurements might be due to the used packages. Is there an easy way for this? The best way I can think of right now is saving the names of installed packages out of VIPMs program data folder.
-
Every time you build a VI Package, you are prompted to specify release notes. These are not very usable at the moment though. To read these, you need to right click on the package, select "Get Info" and then read the specific version's release notes. If you're catching up on a new version of package that's more than a couple versions newer than what you've been using, it can take a long time to understand what the impacts to that package are. I would like to propose VIPM have an option to view aggregated release notes. This would be exposed in a right click option on a given package, and aggregate all individual release notes for all versions of the package that are in the library. The goal would be to have an easy way to see something like the following: My Package v2.0.0.1 - New Release with some groundbreaking features v1.2.0.1 - Minor update made to feature Z v1.1.1.1 - Patch for bug X v1.1.0.0 - Minor update to add feature Y v1.0.0.0 - First release of my cool tool