Rooba
/
mitmproxy
mirror of https://github.com/mitmproxy/mitmproxy.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity
mitmproxy/release
History
Aldo Cortesi d9752c90f9 Remove support for Python 3.5 
There are a number of significant improvements in Python3.6 - especially in
asyncio - that makes ditching Python 3.5 compelling. The next Ubuntu LTS will
be released before the next version of mitmproxy, and will include Python 3.6
in base.

This patch removes support for testing under Python 3.5 and changes our
documentation. There are deeper changes in the type system and so forth that we
will make over time.
 		2018-04-01 09:46:32 +12:00
..
hooks fix appveyor build script 2017-12-30 18:48:49 +01:00
installbuilder InstallBuilder (#1826) 2016-12-11 23:07:47 +01:00
specs fix pyinstaller 2016-11-28 00:51:52 +01:00
windows-store-experiment minor fixes for windows package 2017-06-14 14:35:51 +02:00
.gitignore pin snapshot server hostkey, update pysftp 2018-01-04 14:12:30 +01:00
README.md Remove support for Python 3.5 2018-04-01 09:46:32 +12:00
ci.py release: fix PR detection for appveyor 2018-03-08 09:52:05 +13:00
rtool.py release: clean rtool 2018-03-07 22:50:07 +13:00

README.md

Release Checklist

Make sure run all these steps on the correct branch you want to create a new release for!

  • Verify mitmproxy/version.py
  • Update CHANGELOG
  • Verify that all CI tests pass
  • Tag the release and push to Github
    • For alphas, betas, and release candidates, use lightweight tags. This is necessary so that the .devXXXX counter does not reset.
    • For final releases, use annotated tags. This makes the .devXXXX counter reset.
  • Wait for tag CI to complete

GitHub Release

PyPi

  • tox -e rtool -- upload-release

Homebrew

  • tox -e rtool -- homebrew-pr
  • The Homebrew maintainers are typically very fast and detect our new relese within a day, but we can be a nice citizen and create the PR ourself.

Docker

  • Update docker-releases repo
    • Create a new branch based of master for major versions.
    • Update the dependencies in alpine/requirements.txt
      • Creating a fresh venv, pip-installing the new wheel in there, and then export all packages:
      • virtualenv -ppython3.6 venv && source venv/bin/activate && pip install mitmproxy && pip freeze
    • Tag the commit with the correct version
      • 2.0.0 for new major versions
      • 2.0.2 for new patch versions
  • Update latest tag here
  • Check that the build for this tag succeeds https://hub.docker.com/r/mitmproxy/mitmproxy/builds/
  • If build failed:
    • Fix it and commit
    • git tag 3.0.2 the new commit
    • git push origin :refs/tags/3.0.2 to delete the old remote tag
    • git push --tags to push the new tag
    • Check the build details page again

Prepare for next release