diff options
| author | kira0204 <rshtmudgal@gmail.com> | 2018-02-24 12:42:21 +0530 |
|---|---|---|
| committer | kira0204 <rshtmudgal@gmail.com> | 2018-02-24 12:42:21 +0530 |
| commit | 8209b89d41bdfc3b6a9a3dd5d9054b02722e0d4f (patch) | |
| tree | 5691f1dd11ac1b2a98e57ed06252ff7dc40cd555 /release | |
| parent | 69dbd1da61e6e452da63c63fba1d810b269f459d (diff) | |
| parent | eee109117f956600261bc938be52040d1474a97f (diff) | |
| download | mitmproxy-8209b89d41bdfc3b6a9a3dd5d9054b02722e0d4f.tar.gz mitmproxy-8209b89d41bdfc3b6a9a3dd5d9054b02722e0d4f.tar.bz2 mitmproxy-8209b89d41bdfc3b6a9a3dd5d9054b02722e0d4f.zip | |
Merge branch 'master' of https://github.com/kira0204/mitmproxy into update-readme
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. |