This is an automated email from the ASF dual-hosted git repository.

micafer pushed a commit to branch fix_release_guide
in repository https://gitbox.apache.org/repos/asf/libcloud.git

commit 629f059b9aad10835614f9f6db0b755ea4c2b6ee
Author: Miguel Caballer <[email protected]>
AuthorDate: Thu Jan 29 12:07:30 2026 +0100

    Update release guide
---
 docs/committer_guide.rst | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/docs/committer_guide.rst b/docs/committer_guide.rst
index 6faf0fb00..36fe357b1 100644
--- a/docs/committer_guide.rst
+++ b/docs/committer_guide.rst
@@ -117,7 +117,7 @@ To run it:
 your local GPG database.
 
 This should result in a set of
-``apache-libcloud-${VERSION}.{tar.gz,whl}{,asc,md5,sha1}`` files that
+``apache-libcloud-${VERSION}.{tar.gz,whl}{,asc,sha256,sha512}`` files that
 are suitable to be uploaded for a release.
 
 Copy the artifacts in another directory, unpack one of them and test it with 
``tox``.
@@ -140,8 +140,9 @@ For example:
 5. Upload the release artifacts and start a [VOTE] thread
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Upload all release artifacts including the ``whl`` files to your 
people.apache.org
-space. Then start a [VOTE] thread on the [email protected] mailing list.
+Upload all release artifacts including the ``whl`` files to the dist dev SVN
+repository at https://dist.apache.org/repos/dist/dev/libcloud/. Then start a
+[VOTE] thread on the [email protected] mailing list.
 
 Once the vote has passed tag the release with a new tag, removing the 
``-tentative`` postfix.
 Upload the release artifacts to Apache servers and Pypi.
@@ -161,7 +162,7 @@ key.
 6. Uploading release artifacts to Apache servers
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-* Add release artifacts to the dist SVN repository at
+* Add release artifacts to the release dist SVN repository at
   https://dist.apache.org/repos/dist/release/libcloud/
 
   It may take up to a day for the artifacts to be available on all the

Reply via email to