You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@libcloud.apache.org by to...@apache.org on 2013/12/12 16:28:12 UTC

[1/2] git commit: Fix a typo in the docs.

Updated Branches:
  refs/heads/trunk 3b1888733 -> 9ac9ed17f


Fix a typo in the docs.


Project: http://git-wip-us.apache.org/repos/asf/libcloud/repo
Commit: http://git-wip-us.apache.org/repos/asf/libcloud/commit/031f1538
Tree: http://git-wip-us.apache.org/repos/asf/libcloud/tree/031f1538
Diff: http://git-wip-us.apache.org/repos/asf/libcloud/diff/031f1538

Branch: refs/heads/trunk
Commit: 031f15389d90370f6398cbec026b19b9b6ae7f53
Parents: 3b18887
Author: Tomaz Muraus <to...@apache.org>
Authored: Thu Dec 12 16:22:55 2013 +0100
Committer: Tomaz Muraus <to...@apache.org>
Committed: Thu Dec 12 16:22:55 2013 +0100

----------------------------------------------------------------------
 docs/committer_guide.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/libcloud/blob/031f1538/docs/committer_guide.rst
----------------------------------------------------------------------
diff --git a/docs/committer_guide.rst b/docs/committer_guide.rst
index 660dd6c..ca13248 100644
--- a/docs/committer_guide.rst
+++ b/docs/committer_guide.rst
@@ -114,7 +114,7 @@ For example:
 For consistency and security reasons packages are always uploaded to PyPi
 manually using the web interface and not using the ``setup.py upload`` command.
 
-* Run ``python setup.py register upload`` command. This will register a new
+* Run ``python setup.py register`` command. This will register a new
   version on PyPi, but it won't upload the actual release artifacts.
 
 * Go to the `PyPi release management page`_, find a new release and click on


[2/2] git commit: docs: Update "releasing" section.

Posted by to...@apache.org.
docs: Update "releasing" section.


Project: http://git-wip-us.apache.org/repos/asf/libcloud/repo
Commit: http://git-wip-us.apache.org/repos/asf/libcloud/commit/9ac9ed17
Tree: http://git-wip-us.apache.org/repos/asf/libcloud/tree/9ac9ed17
Diff: http://git-wip-us.apache.org/repos/asf/libcloud/diff/9ac9ed17

Branch: refs/heads/trunk
Commit: 9ac9ed17f3a3d3bb10336879eed54593927aa7a6
Parents: 031f153
Author: Tomaz Muraus <to...@apache.org>
Authored: Thu Dec 12 16:27:47 2013 +0100
Committer: Tomaz Muraus <to...@apache.org>
Committed: Thu Dec 12 16:27:47 2013 +0100

----------------------------------------------------------------------
 docs/committer_guide.rst | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/libcloud/blob/9ac9ed17/docs/committer_guide.rst
----------------------------------------------------------------------
diff --git a/docs/committer_guide.rst b/docs/committer_guide.rst
index ca13248..6b73f3f 100644
--- a/docs/committer_guide.rst
+++ b/docs/committer_guide.rst
@@ -132,6 +132,26 @@ screenshot bellow.
    :width: 700px
    :align: center
 
+6. Verifying the release artifact check sums
+
+To verify that nothing went wrong doing the release process, run the
+``./dist/verify_checksums.sh`` script.
+
+This script downloads the release artifacts from the Apache and PyPi server and
+makes sure that the MD5 check sums of the both files match.
+
+Usage:
+
+.. sourcecode:: bash
+
+    ./dist/verify_checksums <version>
+
+For example
+
+.. sourcecode:: bash
+
+    ./dist/verify_checksums apache-libcloud-0.13.2
+
 7. Updating doap_libcloud.rdf file
 
 Add information about the new release to the ``doap_libcloud.rdf`` file in the