I don’t think the EOL of CPython 2.7 should necessarily bother anyone using IronPython. It’s not like IronPython depends on CPython in any way, or is exposed to any CPython bugs or vulnerabilities. I can see it from a standardisation point if view of course.
True, IronPython3 isn't ready and with 2.7 EOL I would say that it may not be a great fit for someone currently weighing up their options between it and pythonnet to use in a current project.
Development on IP3 is, however, still very alive and active so I wouldn't consider the entire project dead: