From 6c8e0469aca20dd595887606835a49e902f7a0e4 Mon Sep 17 00:00:00 2001 From: Nathan Neulinger Date: Wed, 13 Feb 2019 19:49:45 -0600 Subject: [PATCH] add new release process doc --- README.release.md | 13 +++++++++++++ src/README-RELEASE | 10 ---------- 2 files changed, 13 insertions(+), 10 deletions(-) create mode 100644 README.release.md delete mode 100644 src/README-RELEASE 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. diff --git a/src/README-RELEASE b/src/README-RELEASE deleted file mode 100644 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} -- 2.40.0