mitmproxy/release
Aldo Cortesi c774a9fec9 python3: clean up super and __future__ 2016-10-17 18:03:07 +13:00
..
specs Add icon for binaries 2016-03-11 20:30:17 +05:30
.gitignore move bin into release, update rtool 2016-02-18 11:25:29 +01:00
README.mkd Bump to 0.18.1 to fix pypi obstreperousness 2016-10-16 23:52:47 +13:00
rtool.pem add release 2016-02-15 14:58:53 +01:00
rtool.py python3: clean up super and __future__ 2016-10-17 18:03:07 +13:00
setup.py test & examples: zap six 2016-10-17 16:45:45 +13:00

README.mkd

Release policies

  • By default, every release is a new minor (0.x) release and it will be pushed for all three projects.

  • Only if an emergency bugfix is needed, we push a new 0.x.y bugfix release for a single project. This matches with what we do in setup.py:

    "netlib>=%s, <%s" % (version.MINORVERSION, version.NEXT_MINORVERSION)
    

Release Checklist

  • Verify that all CI tests pass for current master
  • Tag the release, and push to Github
  • Wait for tag CI to complete
  • Download assets from snapshots.mitmproxy.org
  • Create release notice on Github
  • Upload wheel to pypi