diff options
| author | ColdFire <9128903+fenilgandhi@users.noreply.github.com> | 2018-02-23 00:27:10 +0530 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-02-23 00:27:10 +0530 |
| commit | 777cb98a86f3e8883383935661e2ed20ed9b6bd4 (patch) | |
| tree | 67d3e1259dccb83866496f45fe20ac3bd76961ce /release | |
| parent | 6bf250aa3e8ede84d16170d95728c6488444a5a8 (diff) | |
| parent | 58ccad7576e5fd33e937aba58df2f9edc389e52e (diff) | |
| download | mitmproxy-777cb98a86f3e8883383935661e2ed20ed9b6bd4.tar.gz mitmproxy-777cb98a86f3e8883383935661e2ed20ed9b6bd4.tar.bz2 mitmproxy-777cb98a86f3e8883383935661e2ed20ed9b6bd4.zip | |
Merge branch 'master' into issue-2872
Diffstat (limited to 'release')
| -rw-r--r-- | release/README.md | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/release/README.md b/release/README.md index 7bb89638..2b709318 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. |