- 1.3.3rel_1_3_3

4 files changed, 32 insertions, 30 deletions

diff --git a/docs/build/changelog.rst b/docs/build/changelog.rst
index f3015e6..f18500c 100644
--- a/docs/build/changelog.rst
+++ b/docs/build/changelog.rst
@@ -5,7 +5,36 @@ Changelog
 
 .. changelog::
     :version: 1.3.3
-    :include_notes_from: unreleased
+    :released: January 22, 2020
+
+    .. change::
+        :tags: bug, postgresql
+        :tickets: 637
+
+        Fixed issue where COMMENT directives for PostgreSQL failed to correctly
+        include an explicit schema name, as well as correct quoting rules for
+        schema, table, and column names.  Pull request courtesy Matthew Sills.
+
+    .. change::
+        :tags: usecase, operations
+        :tickets: 624
+
+        Added support for rendering of "computed" elements on :class:`.Column`
+        objects, supported in SQLAlchemy via the new :class:`.Computed` element
+        introduced in version 1.3.11. Pull request courtesy Federico Caselli.
+
+        Note that there is currently no support for ALTER COLUMN to add, remove, or
+        modify the "GENERATED ALWAYS AS" element from a column;  at least for
+        PostgreSQL, it does not seem to be supported by the database. Additionally,
+        SQLAlchemy does not currently reliably reflect the "GENERATED ALWAYS AS"
+        phrase from an existing column, so there is also no autogenerate support
+        for addition or removal of the :class:`.Computed` element to or from an
+        existing column, there is only support for adding new columns that include
+        the :class:`.Computed` element.  In the case that the :class:`.Computed`
+        element is removed from the :class:`.Column` object in the table metadata,
+        PostgreSQL and Oracle currently reflect the "GENERATED ALWAYS AS"
+        expression as the "server default" which will produce an op that tries to
+        drop the element as a default.
 
 .. changelog::
     :version: 1.3.2
diff --git a/docs/build/conf.py b/docs/build/conf.py
index 4aad627..cb62964 100644
--- a/docs/build/conf.py
+++ b/docs/build/conf.py
@@ -85,8 +85,8 @@ copyright = u"2010-2020, Mike Bayer"  # noqa
 # The short X.Y version.
 version = alembic.__version__
 # The full version, including alpha/beta/rc tags.
-release = "1.3.2"
-release_date = "December 16, 2019"
+release = "1.3.3"
+release_date = "January 22, 2020"
 
 
 # The language for content autogenerated by Sphinx. Refer to documentation
diff --git a/docs/build/unreleased/624.rst b/docs/build/unreleased/624.rst
deleted file mode 100644
index a10967b..0000000
--- a/docs/build/unreleased/624.rst
+++ /dev/null
@@ -1,20 +0,0 @@
-.. change::
-    :tags: usecase, operations
-    :tickets: 624
-
-    Added support for rendering of "computed" elements on :class:`.Column`
-    objects, supported in SQLAlchemy via the new :class:`.Computed` element
-    introduced in version 1.3.11. Pull request courtesy Federico Caselli.
-
-    Note that there is currently no support for ALTER COLUMN to add, remove, or
-    modify the "GENERATED ALWAYS AS" element from a column;  at least for
-    PostgreSQL, it does not seem to be supported by the database. Additionally,
-    SQLAlchemy does not currently reliably reflect the "GENERATED ALWAYS AS"
-    phrase from an existing column, so there is also no autogenerate support
-    for addition or removal of the :class:`.Computed` element to or from an
-    existing column, there is only support for adding new columns that include
-    the :class:`.Computed` element.  In the case that the :class:`.Computed`
-    element is removed from the :class:`.Column` object in the table metadata,
-    PostgreSQL and Oracle currently reflect the "GENERATED ALWAYS AS"
-    expression as the "server default" which will produce an op that tries to
-    drop the element as a default.
diff --git a/docs/build/unreleased/637.rst b/docs/build/unreleased/637.rst
deleted file mode 100644
index a30afb7..0000000
--- a/docs/build/unreleased/637.rst
+++ /dev/null
@@ -1,7 +0,0 @@
-.. change::
-    :tags: bug, postgresql
-    :tickets: 637
-
-    Fixed issue where COMMENT directives for PostgreSQL failed to correctly
-    include an explicit schema name, as well as correct quoting rules for
-    schema, table, and column names.  Pull request courtesy Matthew Sills.