From a9d5757da06f7e9edce21bc2dac14e2f3e8ce77f Mon Sep 17 00:00:00 2001 From: Maximilian Hils Date: Thu, 22 Feb 2018 14:21:46 +0100 Subject: [PATCH] update release instructions --- release/README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/release/README.md b/release/README.md index 7bb896388..2b7093184 100644 --- a/release/README.md +++ b/release/README.md @@ -27,7 +27,8 @@ Make sure run all these steps on the correct branch you want to create a new rel - Tag the commit with the correct version * `2.0.0` for new major versions * `2.0.2` for new patch versions - * `2.0` always points to the latest patch version of the `2.0.x` series (update tag + force push) - Update `latest` tag [here](https://hub.docker.com/r/mitmproxy/mitmproxy/~/settings/automated-builds/) -After everything is done, you might want to bump the version on master in [https://github.com/mitmproxy/mitmproxy/blob/master/mitmproxy/version.py](mitmproxy/version.py) if you just created a major release. +## 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.