haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Explain that older Vagrant plugin licenses may not work with new VMware 

This is the result of an unhappy customer who raised a very valid point. If you
are not on the Vagrant mailing list, you would be unaware that upgrading VMware
would cause your plugin to stop functioning.

While this does not solve the problem of dispersing that information, it helps
clarify that plugin version support is for the latest version of the Vagrant
plugin and does not extend to previous ones.
This commit is contained in:
Seth Vargo 2014-11-04 10:44:44 -05:00
parent 1464a63928
commit 8f59f89a2e
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
website/www/source/vmware/index.html.erb
View File

@ -176,6 +176,9 @@ page_title: "VMware Vagrant Environments"
The provider license does not include a license to the VMware
software, which must be purchased separately. If you're buying over 100 licenses, contact <a href="mailto:sales@hashicorp.com">sales@hashicorp.com</a> for volume pricing.
</div>
<div class="subtext">
Previous plugin versions may not support the latest VMware products. Please visit <a href="http://license.hashicorp.com/upgrade/vmware<%= Time.now.year %>">the license upgrade center</a> to check if your license requires an upgrade before you upgrade your VMware products.
</div>
<div class="subtext">
For reseller information, <a href="/vmware/reseller.html">click here</a>.
</div>