They aren’t done deals. Every manylinuxXXXX PEP requires an indefinite commitment of volunteer resources to keep it updated for as long as Linux distros keep making new releases. See PEP 600 for more discussion 
I definitely appreciate that, but I hope you can understand why I’m going to stay nervous and feel like I have to keep pushing until it’s actually done… Especially since I can’t tell how to get there from here. You said you were accepting manylinux2014 b/c you thought perennial needed more work, but I said at the time that I thought perennial was ready and asked what more work needed to be done, and in the months since then no-one’s been able to answer that. I feel like the only reason it’s even still on the table at all is because I’m pathologically stubborn to the point of self-harm and keep nagging you to pay attention :-/. Not because you’re trying to kill it or anything, but just because inertia is the default state.
I bet if you threaten to accept it then folks will actually offer feedback
And it is kinda frustrating to watch all the one-off work going into manylinux2014 right now, since it’s all going to have to be repeated for the next PEP, when (it seems to me) we had a PEP ready to go that would have avoided that. All the promises of personpower that I’m aware of applied equally to manylinux2014 and perennial manylinux. The manylinux2014 proponents made clear pretty early on that they were really indifferent between the proposals as long as it let them start shipping CentOS 7 wheels on a reasonable time-frame. They just feared that we wouldn’t be able to get agreement on the better solution, and that became something of a self-fulfilling prophecy. (Edit: Not saying that’s the only reason that perennial stalled, just that it was a contributing factor.)