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

website/docs: document how long compatibility will be aroung

This commit is contained in:
Mitchell Hashimoto 2013-11-23 14:14:01 -08:00
parent 8a0f209f3f
commit 7aa3a3967d
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
website/docs/source/v2/installation/backwards-compatibility.html.md
View File

@ -12,6 +12,12 @@ Vagrantfiles which don't use plugins. After installing Vagrant 1.1, your 1.0.x e
continue working without modifications, and existing running machines will continue working without modifications, and existing running machines will
continue to be managed properly. continue to be managed properly.
This compatibility layer will remain in Vagrant up to and including Vagrant 2.0.
It may still exist after that, but Vagrant's compatibility promise is only for
two versions. Seeing that major Vagrant releases take years to develop and
release, it is safe to stick with your version 1.0.x Vagrantfile for the
time being.
If you use any Vagrant 1.0.x plugins, you must remove references to these from If you use any Vagrant 1.0.x plugins, you must remove references to these from
your Vagrantfile prior to upgrading. Vagrant 1.1+ introduces a new plugin your Vagrantfile prior to upgrading. Vagrant 1.1+ introduces a new plugin
format that will protect against this sort of incompatibility from ever format that will protect against this sort of incompatibility from ever