update to try to document versioning policy

diff --git a/README.release.md b/README.release.md
index 0c6733726b401200ec107179225b23c2e9c4cffc..093206bdecb1a7839b3e33fda413f6a45e700992 100644 (file)
--- a/README.release.md
+++ b/README.release.md
@@ -1,13 +1,14 @@
 Release Process
 ===============
 
-During development, version/tags/etc. should reflect version "2.9.x" for example
+Follow semantic versioning standard if at all possible: https://semver.org/ (MAJOR.MINOR.PATCH-PRE)
 
-At time of release, create ONE commit with all version numbers update in files and named for example "X.X.X".
-Create a tag of the name "cracklib-X.Y.Z" pointed to that commit and produce releases at that point
+During development, pick next planned version - increment patch level, and add "-dev"
 
-Before publication, you can add in NEWS for example "2.9.x" or "master" or "dev" and only when it is the commit
+Before publication, add in NEWS for example "2.9.x" or "master" or "dev" and only when it is the commit
 for announcement, the moment to change the new version.
 
-After the release, when you add improvement in the code, "2.9.x" or "master" or "dev", do not mark with next version
-number to avoid future confusion.
+At time of release, create ONE commit with all version numbers update in files and named for example "X.X.X".
+Create a tag of the name "vX.Y.Z" pointed to that commit and produce releases at that point
+
+After the release, commit a change to put versions back to MAJOR.MINOR.(PATCH+1)-dev