blob: 8b37df789ed61f2dbdde506a5c411927f409d373 [file] [log] [blame]
Alex Stapletonc5fffd32014-03-18 15:29:00 +00001Doing a release
Alex Gaynor89063f62014-01-06 15:52:38 -08002===============
3
4Doing a release of ``cryptography`` is a two part process.
5
6Bumping the version number
7--------------------------
8
9The first step in doing a release is bumping the version number in the
10software.
11
Alex Gaynorce0b5a32014-01-06 16:53:31 -080012* Update the version number in ``cryptography/__about__.py``.
Alex Gaynor3f230402014-01-08 09:21:57 -080013* Set the release date in the :doc:`/changelog`.
Alex Gaynor89063f62014-01-06 15:52:38 -080014* Do a commit indicating this.
15* Send a pull request with this.
16* Wait for it to be merged.
17
18Performing the release
19----------------------
20
Alex Stapleton63b3de22014-02-08 09:43:16 +000021The commit that merged the version number bump is now the official release
Alex Gaynorb3794db2014-01-07 09:25:54 -080022commit for this release. You will need to have ``gpg`` installed and a ``gpg``
23key in order to do a release. Once this has happened:
Alex Gaynor89063f62014-01-06 15:52:38 -080024
25* Run ``invoke release {version}``.
26
Alex Gaynorfea893c2014-01-07 11:06:51 -080027The release should now be available on PyPI and a tag should be available in
28the repository. You should verify that ``pip install cryptography`` works
Alex Gaynor41c14d52014-01-07 11:19:08 -080029correctly:
30
31.. code-block:: pycon
32
33 >>> import cryptography
34 >>> cryptography.__version__
35 '...'
36
37Verify that this is the version you just released.