aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAlex Gaynor <alex.gaynor@gmail.com>2014-01-07 11:19:08 -0800
committerAlex Gaynor <alex.gaynor@gmail.com>2014-01-07 11:19:08 -0800
commit41c14d55ea2d17e3e9968acfa93d442615f7cda0 (patch)
tree7a8c94b417cf4bad7ab18b029f25aaaea678c1ed
parent4345c0d3e65132985afb3f5a7fee04ea212811a0 (diff)
downloadcryptography-41c14d55ea2d17e3e9968acfa93d442615f7cda0.tar.gz
cryptography-41c14d55ea2d17e3e9968acfa93d442615f7cda0.tar.bz2
cryptography-41c14d55ea2d17e3e9968acfa93d442615f7cda0.zip
How to verify that your released correctly
-rw-r--r--docs/doing-a-release.rst10
1 files changed, 9 insertions, 1 deletions
diff --git a/docs/doing-a-release.rst b/docs/doing-a-release.rst
index e52c2728..0f382064 100644
--- a/docs/doing-a-release.rst
+++ b/docs/doing-a-release.rst
@@ -25,4 +25,12 @@ key in order to do a release. Once this has happened:
The release should now be available on PyPI and a tag should be available in
the repository. You should verify that ``pip install cryptography`` works
-correctly.
+correctly:
+
+.. code-block:: pycon
+
+ >>> import cryptography
+ >>> cryptography.__version__
+ '...'
+
+Verify that this is the version you just released.