aboutsummaryrefslogtreecommitdiffstats
path: root/release/README.md
diff options
context:
space:
mode:
authorThomas Kriechbaumer <thomas@kriechbaumer.name>2018-02-25 17:49:54 +0100
committerThomas Kriechbaumer <thomas@kriechbaumer.name>2018-02-25 17:49:54 +0100
commit1f95b8375d9f7f09d0753b4e01792644d12bc08d (patch)
tree97cab2f9dc51c0790c85a5144097a5da9328c4f5 /release/README.md
parent2db8a087eba27d294203d621134aa4f29c68b4f3 (diff)
downloadmitmproxy-1f95b8375d9f7f09d0753b4e01792644d12bc08d.tar.gz
mitmproxy-1f95b8375d9f7f09d0753b4e01792644d12bc08d.tar.bz2
mitmproxy-1f95b8375d9f7f09d0753b4e01792644d12bc08d.zip
improve release instructions
Diffstat (limited to 'release/README.md')
-rw-r--r--release/README.md11
1 files changed, 5 insertions, 6 deletions
diff --git a/release/README.md b/release/README.md
index 67a23c02..b2f97aab 100644
--- a/release/README.md
+++ b/release/README.md
@@ -16,7 +16,11 @@ Make sure run all these steps on the correct branch you want to create a new rel
- Attach all files from the new release folder on https://snapshots.mitmproxy.org
## PyPi
-- Upload wheel to pypi: `twine upload <mitmproxy-...-.whl`
+- `tox -e rtool -- upload-release`
+
+## Homebrew
+- `tox -e rtool -- homebrew-pr`
+- The Homebrew maintainers are typically very fast and detect our new relese within a day, but we can be a nice citizen and create the PR ourself.
## Docker
- Update docker-releases repo
@@ -36,11 +40,6 @@ Make sure run all these steps on the correct branch you want to create a new rel
- `git push --tags` to push the new tag
- Check the build details page again
-## Homebrew
-- The Homebrew maintainers are typically very fast and detect our new relese within a day
-- If you want to speed this up:
- - `brew bump-formula-pr --url=https://github.com/mitmproxy/mitmproxy/archive/v3.0.2.tar.gz mitmproxy`
-
## Prepare for next release
- Last but not least, bump the version on master in [https://github.com/mitmproxy/mitmproxy/blob/master/mitmproxy/version.py](mitmproxy/version.py) for major releases.