diff options
| author | Maximilian Hils <git@maximilianhils.com> | 2018-02-22 14:21:46 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-02-22 14:21:46 +0100 |
| commit | a9d5757da06f7e9edce21bc2dac14e2f3e8ce77f (patch) | |
| tree | 01365ab96752f0047d4d0ad8c6b365a314ea93cb /release | |
| parent | 4356430aa36a70d02aa66cb60545b74a14d460e2 (diff) | |
| download | mitmproxy-a9d5757da06f7e9edce21bc2dac14e2f3e8ce77f.tar.gz mitmproxy-a9d5757da06f7e9edce21bc2dac14e2f3e8ce77f.tar.bz2 mitmproxy-a9d5757da06f7e9edce21bc2dac14e2f3e8ce77f.zip | |
update release instructions
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. |