Changes between Version 156 and Version 157 of TracDev/ReleaseChecklist

Timestamp:

May 26, 2020, 5:39:36 PM (4 years ago)

Author:

Ryan J Ollos

Comment:

Just always increment the micro version for simplicity.

TracDev/ReleaseChecklist

@@ -7 +7 @@
 The //major.minor.micro// semantic versioning scheme is followed, with guidance from PEP:0440. However, since the //major// version is rarely incremented, we generally refer to a 1.x release a //major// release and a 1.x.y release a //minor// release.
 
-In the event that a critical defect is discovered after a release is made, the //micro// version number should be incremented and a new //minor// release created. In the event that a packaging or distribution error results in the need to generate a new package name, a [PEP:0440#post-releases post-release] identifier should be added, starting with `post1`. The post-release identifier is added by editing `tag_build` in [browser:/trunk/setup.cfg setup.cfg].
-
-For example, a filename cannot be reused when uploading to PyPI [https://mail.python.org/pipermail/distutils-sig/2015-January/025683.html more than once], so a post-release is necessary in the event of a packaging or uploading error.
+In the event that a defect or packaging distribution error is discovered after a release is made, the //micro// version number should be incremented and a new //minor// release created.
+
+A filename cannot be reused when uploading to PyPI [https://mail.python.org/pipermail/distutils-sig/2015-January/025683.html more than once], so the micro version must be incremented in the event of a packaging or uploading error.