Fixed #428 -- added a changelog

docs/changelog.rst

@@ -0,0 +1,9 @@
+Changelog
+=========
+
+0.1
+~~~
+
+**Released on XXX**
+
+* Initial released.

docs/contributing.rst

@@ -29,6 +29,8 @@ devastating, ``cryptography`` has a strict code review policy:
   backwards incompatible release of a dependency) no pull requests may be
   merged until this is rectified.
 * All merged patches must have 100% test coverage.
+* New features and significant bug fixes should be documented in the
+  :doc:`/changelog`.
 
 The purpose of these policies is to minimize the chances we merge a change
 which jeopardizes our users' security.

docs/doing-a-release.rst

@@ -10,6 +10,7 @@ The first step in doing a release is bumping the version number in the
 software.
 
 * Update the version number in ``cryptography/__about__.py``.
+* Set the release date in the :doc:`/changelog`.
 * Do a commit indicating this.
 * Send a pull request with this.
 * Wait for it to be merged.

docs/index.rst

@@ -80,4 +80,5 @@ The ``cryptography`` open source project
     security
     api-stability
     doing-a-release
+    changelog
     community