Yes, it wasn’t perfectly phrased.
You have to realize the April release is at the request of the release manager and is expected to be no different than the code that exists in the 2.7 branch as of 2020-01-01. Basically it is easier on the people involved who have been carrying Python 2.7 forward for over a decade – RMs start their work the day the last feature release came out which for 2.6.0 is 2008-10-01, and for Benjamin that’s over a third of his lifetime – and adds some catharsis to basically click the buttons to do the final release at PyCon US with the dev team in the room. If some absolutely horrible release-blocker bug that will cause the world to collapse comes in it could get fixed before then, but for all intents and purposes the Python 2.7 is in a protracted RC period and EOL’ed. IOW you can’t even get a spelling mistake fixed at this point and so the implication for you and your company is the same: you are not getting any upstream support anymore for Python 2.7 whether released yesterday or in less than 4 months time.
I understand being upset if you’re worried this going to cause you issues at work, but please do realize your phrasing comes off as not considering our needs and desires as the people who kept Python 2.7 running for as long as we have. Had you simply asked “why is the final release not on 2020-01-01?” then it wouldn’t come off as quite so hostile.