Jump to content

Steven Dusing

Members
  • Content Count

    4
  • Joined

  • Last visited

Everything posted by Steven Dusing

  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 ag
  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 ident
×
×
  • Create New...

Important Information

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