add new release process doc

diff --git a/README.release.md b/README.release.md
new file mode 100644 (file)
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.

diff --git a/src/README-RELEASE b/src/README-RELEASE
deleted file mode 100644 (file)
index 07d5702..0000000
--- a/src/README-RELEASE
+++ /dev/null
@@ -1,10 +0,0 @@
-configure
-make dist
-
-ver=$(head -1 NEWS)
-ver=${ver#v}
-echo "creating ${ver} release"
-
-echo "use the web UI to upload tarball"
-
-svn copy -m "tag at ${ver}" svn+ssh://nneul@svn.code.sf.net/p/cracklib/code/trunk/cracklib svn+ssh://nneul@svn.code.sf.net/p/cracklib/code/tags/cracklib-${ver}