Including manylinux2010 in readme

[armudgal]

Hi there,
As mentioned in #179.
I am not sure as manylinux2010 will be replacing manylinux1 or we still want to mention manylinux1 in the readme.

According to me:

README should majorly talk about manylinux2010 and include manylinux1 briefly
but since manylinux2010 is in demo phase, would that be a good idea?

Looking for opinions and suggestions.
Thanks

PS: Did a blunder in commit message, fixing it

[mayeut]

@armudgal, I agree that README in master should majorly talk about manylinux2010. I think a link shall be added to the manylinux1 branch in order to redirect people that want information on manylinux1 to that specific branch.

[armudgal]

Sure thanks. I will make the required changes.

[trishankatdatadog]

Speaking of which, can someone with admin superpowers (maybe @njsmith) make the manylinux1 a GitHub protected branch, so that no one can push to it directly, but need to make PRs that must be reviewed and so on?

[armudgal]

One bottleneck for this PR would be to merge pypa/python-manylinux-demo#19 first, so that the demo is on the same page with this repository.

[mayeut]

My previous comment still applies on the newer commit.
PEP 571 also defines the manylinux2010_i686 platform tag even though we don't have an image for this (yet).
It should read:

This was further enhanced by `PEP 571 <https://www.python.org/dev/peps/pep-0571/>`_
defining ``manylinux2010_x86_64`` and ``manylinux2010_i686`` platform tags.

[mayeut]

@armudgal,
There's still a reference to PEP 513in the docker image content. Can you change that as well please ?

[mayeut]

@armudgal, your commit mentions Updating PEP number in Docker image content but I'm not seeing any diffs in the file for that part.

[armudgal]

I did not stage that file by mistake. Apologies 🙉

[mayeut]

LGTM thanks.