I've accepted the manylinux2010 PEP, so that's now an active interoperability standard: https://www.python.org/dev/peps/pep-0571/

However, there are a number of further steps needed before folks can actually make use of that new baseline, and the order of operations matters (since building manylinux2010 wheels isn't very useful if installers won't install them):

Essential client support:

• Update pip 19.0 to install manylinux2010 wheels (PR: Manylinux2010 pip#5410)
• Update pip 9.x to install manylinux2010 wheels (needed to avoid the manylinux2010 rollout being delayed by the Python API break between pip 9.x and pip 10.x) (@ncoghlan: skip for now, wait and see if we get complaints about needing this)
• Update pipenv to install manylinux2010 wheels (needed due to pipenv vendoring pip, so the support depends on the version of pipenv being used, rather than the version of pip in the host or target environments)

Enable publication of manylinux2010 wheel archives:

• Update auditwheel to emit manylinux2010 wheel archives (PR: Manylinux2010 auditwheel#92)
• Confirm that twine will upload manylinux2010 wheel archives
• Update warehouse to accept manylinux2010 wheel uploads (Allow manylinux2010 wheel upload pypi/warehouse#3951)
• Provide a manylinux2010 build environment: https://quay.io/repository/pypa/manylinux2010_x86_64

Management of transition from manylinux1:

• Update https://packaging.python.org/specifications/platform-compatibility-tags/ to cover manylinux2010, with the caveat that it doesn't actually have broad tooling support yet
• Reword the "not yet widely supported" caveat from the platform compatibility tagging page to instead specify the minimum required versions of auditwheel to emit manylinux2010 packages, and pip and pipenv to install them (Update manylinux tags section packaging.python.org#656)
• Nominate a timeline and/or "percentage of PyPI downloads by manylinux2010 compatible installers" for switching the default build environment and auditwheel output to manylinux2010

Additional projects to consider once core capability support has rolled out:

• Option to target manylinux2010 instead of manylinux1 in https://github.com/joerick/cibuildwheel#readme
• Option to target manylinux2010 instead of manylinux1 in https://github.com/matthew-brett/multibuild#readme
• Distinguish manylinux2010 and manylinux1 images in https://github.com/dockcross/dockcross#readme
• ... any other suggestions?

Tagging @takluyver @markrwilliams as the PEP 571 authors, and @di and @brainwane from the PyPI/PSF side of things.