Formalize the release process

1 files changed, 17 insertions, 0 deletions

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