From 8a4a46e7d3a0d05bcb4516af5f210b501fab73df Mon Sep 17 00:00:00 2001 From: Thomas Kriechbaumer Date: Sun, 30 Apr 2017 11:19:55 +0200 Subject: [PATCH] update docker-release tags during release --- release/README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/release/README.md b/release/README.md index 74acc571b..aa770e6e2 100644 --- a/release/README.md +++ b/release/README.md @@ -21,5 +21,9 @@ Make sure run all these steps on the correct branch you want to create a new rel * Creating a fresh venv, pip-installing the new wheel in there, and then export all packages: * `virtualenv -ppython3.5 venv && source venv/bin/activate && pip install mitmproxy && pip freeze` - Update `latest` tag [here](https://hub.docker.com/r/mitmproxy/mitmproxy/~/settings/automated-builds/) +- 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) 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.