diff options
| author | Thomas Kriechbaumer <Kriechi@users.noreply.github.com> | 2017-04-30 11:19:55 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-04-30 11:19:55 +0200 |
| commit | 8a4a46e7d3a0d05bcb4516af5f210b501fab73df (patch) | |
| tree | a22a95ffbc44a1e1751a32e652f6e60f045f7d00 /release | |
| parent | 50cfededce248fac5948a46a00de0bda17c27758 (diff) | |
| download | mitmproxy-8a4a46e7d3a0d05bcb4516af5f210b501fab73df.tar.gz mitmproxy-8a4a46e7d3a0d05bcb4516af5f210b501fab73df.tar.bz2 mitmproxy-8a4a46e7d3a0d05bcb4516af5f210b501fab73df.zip | |
update docker-release tags during release
Diffstat (limited to 'release')
| -rw-r--r-- | release/README.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/release/README.md b/release/README.md index 74acc571..aa770e6e 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. |