Updated documentation for 2.1.0 release.

Author: ramiro

CHANGELOG

@@ -1,7 +1,15 @@
-n.n.n - Unreleased
-==================
-
-- Upgraded tox to 2.9.1, versions >= 2.7.0 can pass PYTHONPATH to test environments again
+2.1.0 - January nn, 2018
+========================
+
+- Upgraded tox to 2.9.1, versions >= 2.7.0 can pass PYTHONPATH to test
+  environments again
+- Updated URL of 'deadsnakes' old Python version PPA respository for Ubuntu
+- Renamed shell aliases so DB backend names in test commands are in sync with
+  Django CI Jenkins jobs
+- Removed Python 2.7 as per Django >= 2.0 Python version support timeline
+- Updated suggested versions of Vagrant and VirtualBox, clarify vbguest plugin
+  suggestion in README file
+- Added a couple of Linux host-specific trobleshooting notes to the README file
 
 2.0.0 - February 18, 2017
 =========================

LICENSE

@@ -1,4 +1,4 @@
-Copyright (c) 2012-2013, Julien Phalip.
+Copyright (c) 2012-2018, Julien Phalip.
 All rights reserved.
 
 Redistribution and use in source and binary forms, with or without
@@ -25,4 +25,4 @@ LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

README.md

@@ -77,7 +77,7 @@ Then, either:
 * Or, if you have already downloaded the box file separately, then run the
   following command in order to import the box into vagrant and boot up the VM:
 
-        (host) $ vagrant box add path/to/django-box-2.0.box --name djangoproject/django-box-2.0
+        (host) $ vagrant box add path/to/django-box-2.1.box --name djangoproject/django-box-2.1
         (host) $ cd django-box
         (host) $ vagrant up
 
@@ -87,10 +87,10 @@ Then, either:
 
   You can download the box file directly from (make sure you update the version
   component):
-  https://atlas.hashicorp.com/djangoproject/boxes/django-box-2.0/versions/2.0.0/providers/virtualbox.box
+  https://atlas.hashicorp.com/djangoproject/boxes/django-box-2.1/versions/2.1.0/providers/virtualbox.box
 
   You can check what the latest released version is here:
-  https://atlas.hashicorp.com/djangoproject/boxes/django-box-2.0/
+  https://atlas.hashicorp.com/djangoproject/boxes/django-box-2.1/
 
 As the VM boots up, it will prompt you to enter your host machine's
 administrator password (the same that you use for logging into your host
@@ -250,7 +250,7 @@ Building a new version
 ----------------------
 
 To upgrade or alter the original box, you'll need to recreate it. You'll need to
-have Ansible 2.1 or greater installed, and django >= 2.0 in a folder beside the
+have Ansible 2.1 or greater installed, and django >= 2.1 in a folder beside the
 django-box project as described above. You should also have
 the [vagrant-vbguest](https://github.com/dotless-de/vagrant-vbguest) plugin
 installed to ensure the correct GuestAdditions are configured within the image.
@@ -263,9 +263,9 @@ The automatic build process will take about 20 minutes. If the new build should
 be saved, then you can package the output:
 
     (host) $ VAGRANT_VAGRANTFILE=Vagrantfile-build vagrant package \
-            --output django-box-2.0.box
+            --output django-box-2.1.box
 
-    (host) $ vagrant box add django-box-2.0.box --name djangoproject/django-box-2.0 # optional - for testing
+    (host) $ vagrant box add django-box-2.1.box --name djangoproject/django-box-2.1 # optional - for testing
 
 Note that compiling a new version should only be required when releasing a new
 build to atlas.hashicorp.com.