From 7aa3a3967dc5518e8fa8751bbb98c36d075373a1 Mon Sep 17 00:00:00 2001 From: Mitchell Hashimoto Date: Sat, 23 Nov 2013 14:14:01 -0800 Subject: [PATCH] website/docs: document how long compatibility will be aroung --- .../source/v2/installation/backwards-compatibility.html.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/website/docs/source/v2/installation/backwards-compatibility.html.md b/website/docs/source/v2/installation/backwards-compatibility.html.md index 4fd4450a2..2166875b1 100644 --- a/website/docs/source/v2/installation/backwards-compatibility.html.md +++ b/website/docs/source/v2/installation/backwards-compatibility.html.md @@ -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 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 your Vagrantfile prior to upgrading. Vagrant 1.1+ introduces a new plugin format that will protect against this sort of incompatibility from ever