diff options
author | Nathan Neulinger <nneul@neulinger.org> | 2019-03-03 11:48:56 -0600 |
---|---|---|
committer | Nathan Neulinger <nneul@neulinger.org> | 2019-03-03 11:48:56 -0600 |
commit | b2f89163a94bc0c4771b89f295135449703a39c3 (patch) | |
tree | ac7207d1c35bbf431b27d71d09850f610b4016b7 /README.release.md | |
parent | 1131782f0b3129faf5126b9597922176024af458 (diff) | |
download | cracklib-b2f89163a94bc0c4771b89f295135449703a39c3.tar.gz |
tweak release process
Diffstat (limited to 'README.release.md')
-rw-r--r-- | README.release.md | 18 |
1 files changed, 10 insertions, 8 deletions
diff --git a/README.release.md b/README.release.md index 0c011a4..c052f4a 100644 --- a/README.release.md +++ b/README.release.md @@ -8,13 +8,15 @@ During development, pick next planned version - increment patch level, and add " 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. -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 +Release process: + 1) Start from a clean repo (git reset --hard; git clean -fdx) + 2) Update version in configure.ac and ../words/Makefile. Update NEWS file to reflect that version. + 3) Run autogen.sh and configure, then 'make dist' + 4) Check for changes, there should be various files updated in po directory - all version number related + 5) Commit that with new version + 6) Create tag of form 'vX.Y.Z' pointed to that commit, push tags + 7) Make in cracklib words directory + 8) Upload the relevant binaries to a release on github attached to the tag that was already created above -To produce release binaries - 1) Start from a clean repo (git reset --hard; git clean -fdx) and run autogen.sh - 2) Configure and 'make dist' - 3) Make in cracklib words directory - 3) Upload the relevant binaries to a release on github attached to the tag that was already created above +After the release, repeat steps 2 through 5 with incremented version: MAJOR.MINOR.(PATCH+1)-dev -After the release, commit a change to put versions to MAJOR.MINOR.(PATCH+1)-dev |