diff options
| author | Nathan Neulinger <nneul@neulinger.org> | 2019-02-13 19:49:45 -0600 |
|---|---|---|
| committer | Nathan Neulinger <nneul@neulinger.org> | 2019-02-13 19:49:45 -0600 |
| commit | 6c8e0469aca20dd595887606835a49e902f7a0e4 (patch) | |
| tree | 358842a59775d74301c748d072ee8f947d51b17b /README.release.md | |
| parent | d17095890504cec8a50037d5a579cb41be1657e5 (diff) | |
| download | cracklib-6c8e0469aca20dd595887606835a49e902f7a0e4.tar.gz | |
add new release process doc
Diffstat (limited to 'README.release.md')
| -rw-r--r-- | README.release.md | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/README.release.md b/README.release.md new file mode 100644 index 0000000..0c67337 --- /dev/null +++ b/README.release.md @@ -0,0 +1,13 @@ +Release Process +=============== + +During development, version/tags/etc. should reflect version "2.9.x" for example + +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 + +Before publication, you can 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. |