Update committer guide
@@ -161,6 +161,9 @@ For example:
git tag --sign v0.15.0 105b9610835f99704996d861d613c5a9a8b3f8b1
+The commit SHA needs to be the one release artifacts are based on (aka the one
+people voted on) and the same one you used for the ``-tentative`` tag.
+
Keep in mind that it's important that you sign the commit / tag with your GPG
key.
@@ -218,12 +221,27 @@ For example
./dist/verify_checksums.sh apache-libcloud-0.13.2
-9. Updating doap_libcloud.rdf file
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+9. Updating doap_libcloud.rdf, __init__.py
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Add information about the new release to the ``doap_libcloud.rdf`` file in the
root of the main code repository.
+Update ``__version__`` attribute in ``libcloud/__init.py__`` file and indicate
+we are now working on a new release by incrementing a number and adding ``dev``
+suffix. For example, if version ``2.2.1`` has been released you would change
+it from:
+
+.. sourcecode:: python
+
+ __version__ = '2.2.1'
+
+To:
+
+.. sourcecode:: python
+
+ __version__ = '2.2.2dev'
+
10. Updating website
~~~~~~~~~~~~~~~~~~~~
