Clarify release steps
@@ -13,12 +13,14 @@ Automated Process
The automated process uses https://pypi.org/project/zest.releaser to perform the correct steps. This is installed by the Pipfile development environment.
-* Clone https://github.com/cekit/cekit.git
+* Clone ``git@github.com:cekit/cekit.git`` (from https://github.com/cekit/cekit)
* Run ``make release`` and follow the prompts.
.. note:: A ``.pypirc`` should be configured according to https://packaging.python.org/specifications/pypirc for PyPi uploads.
+ .. note:: It is recommended to use a 3 digit version specification when prompted (e.g. ``3.9.10``, ``3.10.2``).
+
Manual Process (reference only)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -30,6 +32,7 @@ Manual Process (reference only)
* Push code to master: ``git push upstream master``
* Push tags: ``git push upstream --tags``
* Push a release to PyPi (https://pypi.org/project/cekit/ ) via ``make clean release`` (requires twine: https://pypi.org/project/twine/ which is also available as a RPM in Fedora)
+* Update version on develop to point to next major/minor release
.. note::
Note when you see line like this: Uploading distributions to https://upload.pypi.org/legacy/ enter blindly your username on PyPi and hit enter, it will ask you for password.
@@ -42,5 +45,4 @@ Final Steps
* Write announcement blog post for https://cekit.io/
* Build and submit in Bodhi RPMs for Fedora and EPEL
* Update http://readthedocs.io/ to show new version
-* Update version on develop to point to next major/minor release
* Announce on GChat/Twitter/Email
