angr 8 release tracker

See original GitHub issue

We are almost ready to embrace the future and make angr Python 3 compatible. Doing so means ticking angr version number from 7 to 8, migrating a bunch of modules and projects, and (unfortunately) dropping support for Python 2. We are sure that Python 3 is the future, and the sooner we finish migration, the sooner we can start working on more important and exciting features.

Here is a complete todo list for the angr 8 release.

All involved projects: angr, claripy, CLE, PyVEX, archinfo, Patcherex, fidget, fuzzer, colorguard, angrop, tracer, angr-doc, angr-platforms, angr-management, ailment, and angr-dev.

Rename CFGAccurate to CFGEmulated.
Merge in @subwire 's ARM CFG fixes to py3k branches of PyVEX.
Merge in @subwire 's ARM CFG fixes to py3k branches of angr.
Are there any more compatibility-breaking changes? Now it’s a great time to implement them 😃
For each involved project, make sure all recent PRs and pushes to the master branch are included in the py3k branch.
Move Patcherex from /shellphish to /angr on GitHub. Mark Shellphish/patcherex as deprecated/moved.
For the py3k branch of each involved project, make sure all tests pass on Travis CI.
Update angr’s README.md stating that angr is Python 3 compatible. Python 2 is not supported any more.
Make one last angr 7 release on PyPI. It will be the last angr release that supports Python 2.
Build and upload angr 7 wheels for angr/pyvex on Linux/Windows 32/64-bit.
Write a blog post on this migration. Include a link to the angr 8 migration page in angr-docs.
Update blog post with final angr 7 version number and a pip freeze from the final working installation.
Update angr installation instructions (especially on Windows) in angr-docs.
Shameless self-promotion? 😃
For each involved project, merge the py3k branch into master.
Change release script to use last two digits of year as minor version number.
Release angr 8 on PyPI.
Build and upload angr 8 wheels for angr/pyvex on Linux/Windows 32/64-bit.
Publish blog post.