Jump to content

Steven Dusing

  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Steven Dusing's Achievements


Rookie (2/14)

  • First Post Rare
  • Week One Done
  • One Month Later
  • Conversation Starter Rare

Recent Badges



  1. 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
  2. Currently you have two options for Package Dependency version constraints: >= or == I propose VIPM should use or allow Semantic versioning. That way, if a dependency package has a breaking change, the dependent package can know that it is not compatible with the updated version. This is a big missing piece to VIPM's dependency management, since it currently assumes that a package will forever be able to support future versions of all dependencies, which simply is not the case in real life, as breaking changes do happen from time to time. Allowing for semantic versioning will help identify and prevent breaking code.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.