Merge pull request #86 from caktus/release/1.0.0

Release 1.0.0
caktus · Jun 17, 2020 · 0ff4602 · 0ff4602
2 parents 6f6c602 + 0233d9f
commit 0ff4602
Show file tree

Hide file tree

Showing 6 changed files with 15 additions and 11 deletions.
diff --git a/docs/architecture.rst b/docs/architecture.rst
@@ -60,15 +60,15 @@ from the web servers and delegating them to the worker server for completion.
 * Sample security groups: myproject-sg, myproject-cache-sg, myproject-queue-sg
 
 Database Primary
----------------
+----------------
 
 The database primary server runs PostgreSQL.  It allows encrypted connections
 from the web and worker servers.
 
 * Sample security groups: myproject-sg, myproject-db-sg
 
 Database Replica
---------------
+----------------
 
 The database replica server also runs PostgreSQL, and is setup with streaming
 replication from the primary database server.  This results in very fast

diff --git a/docs/index.rst b/docs/index.rst
@@ -37,6 +37,7 @@ Contents
    troubleshooting
    internals
    useful_commands
+   releases
 
 Indices and tables
 ==================

diff --git a/docs/initial-setup.rst b/docs/initial-setup.rst
@@ -389,10 +389,7 @@ but these are the ones that Fabulaws has most recently been confirmed to work wi
   django-redis-cache==2.1.1
   django-cache-machine==1.1.0
   newrelic==5.12.1.141
-
-In addition, the following requirements are needed for deployment:
-
-.. literalinclude:: ../deploy.in
+  Fabric3
 
 First Deployment
 ----------------

diff --git a/docs/releases.rst b/docs/releases.rst
@@ -0,0 +1,6 @@
+Release History
+===============
+
+* v1.0.0, June 16, 2020
+
+  * Add Python 3 support and drop Python 2 support
diff --git a/docs/troubleshooting.rst b/docs/troubleshooting.rst
@@ -51,7 +51,7 @@ After doing this, be sure to run ``deploy_worker`` (or if it was already
 running, let it complete) so as to restore Celery to a running state again.
 
 Primary database goes down
--------------------------
+--------------------------
 
 If the primary database goes down, manually make sure it's permanently lost
 before converting a replica into the primary.  At this point you probably also
@@ -84,7 +84,7 @@ site::
     fab <environment> end_upgrade
 
 Replica database goes down
--------------------------
+--------------------------
 
 If a replica database goes down, first enable the pretty upgrade message on all
 the web servers::
@@ -104,7 +104,7 @@ site::
     fab <environment> end_upgrade
 
 Adding a new replica
-------------------
+--------------------
 
 If a replica database is lost (either due to promotion to the primary role or
 because it was itself lost), it is desirable to return the application to
@@ -127,7 +127,7 @@ This will take the web servers down one at a time, deploy the latest code,
 and update the settings file to use the newly added database server.
 
 Replica database loses replication connection
--------------------------------------------
+---------------------------------------------
 
 While PostgreSQL administration is outside the scope of this guide, if you
 have determined that a replica database has lost the replication connection

diff --git a/fabulaws/__init__.py b/fabulaws/__init__.py
@@ -1 +1 @@
-__version__ = '0.4.0'
+__version__ = '1.0.0'