From d2fea262c3ef16b2230c4f3db6ff13899bf10dc3 Mon Sep 17 00:00:00 2001 From: Ian Coleman Date: Sat, 5 Aug 2017 15:10:45 +1000 Subject: [PATCH] Formalize the release process --- release_process.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 release_process.md diff --git a/release_process.md b/release_process.md new file mode 100644 index 0000000..4727b9d --- /dev/null +++ b/release_process.md @@ -0,0 +1,17 @@ +Once all code changes for this version have been committed, a release can be +created with the following steps: + +1. Set the version in index.html +1. Update changelog +1. Run `python compile.py` +1. Commit these changes with message `Release vX.Y.Z` +1. Tag the commit `git tag X.Y.Z` +1. Push the changes `git push` +1. Push the new tag `git push --tags` +1. Get the hash of the file `sha256sum bip39-standalone.html` +1. Create the text for the release notes (see prior releases) +1. Sign the release notes `gpg --clearsign /tmp/releasenotes.txt` +1. Create a release on github from the tagged commit + 1. include the signed release notes as text for the release + 1. attach the bip39-standalone.html file +1. Add a new post to twitter from @bip39tool with the version, link and hash -- 2.41.0