diff --git a/CHANGELOG.md b/CHANGELOG.md
index 858d037..80de90c 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,8 @@
-### Unreleased
+### v2.2.0 (2020-01-11)
 
+- Added support for python 3.8
+- Dropped support for python 3.4
+- Added support for flask 1.1
 - Renamed the following methods:
 
   - ``menu.submenu()`` -> ``menu.dir()``
diff --git a/README.md b/README.md
index 85ee923..b177197 100644
--- a/README.md
+++ b/README.md
@@ -81,7 +81,7 @@ if __name__ == '__main__':
 
 ## Installation
 
-This package requires **Python v3.4 or higher**
+This package requires **Python v3.5 or higher**
 
 ```
 pip install flask_gopher
diff --git a/flask_gopher/__version__.py b/flask_gopher/__version__.py
index 55fa725..04188a1 100644
--- a/flask_gopher/__version__.py
+++ b/flask_gopher/__version__.py
@@ -1 +1 @@
-__version__ = '2.1.1'
+__version__ = '2.2.0'
diff --git a/tests/test_flask_gopher.py b/tests/test_flask_gopher.py
index 1da02df..6e24830 100644
--- a/tests/test_flask_gopher.py
+++ b/tests/test_flask_gopher.py
@@ -22,10 +22,6 @@
 
 class TestFunctional(unittest.TestCase):
     """
-    Because the flask_gopher extension is built on hacking the WSGI protocol
-    and the werkzeug HTTP server, I feel that the only way to test that it's
-    working properly is through functional testing.
-
     This class will spin up a complete test flask application and serve it on a
     local TCP port in a new thread. The tests will send real gopher connection
     strings to the server and check the validity of the response body from