diff options
| author | Nathan Neulinger <nneul@neulinger.org> | 2019-02-19 21:01:22 -0600 |
|---|---|---|
| committer | Nathan Neulinger <nneul@neulinger.org> | 2019-02-19 21:01:22 -0600 |
| commit | 6101d17f1d2fc9e5fb62510a68fd8e1874ea6fa6 (patch) | |
| tree | c78391e84c8e87f6d090f0cc648cc002a98968a2 /README.release.md | |
| parent | 865c096ad600a087edb33189af2c51d6bf14d982 (diff) | |
| download | cracklib-6101d17f1d2fc9e5fb62510a68fd8e1874ea6fa6.tar.gz | |
update to try to document versioning policy
Diffstat (limited to 'README.release.md')
| -rw-r--r-- | README.release.md | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/README.release.md b/README.release.md index 0c67337..093206b 100644 --- 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 |