Was it the same wise-man who also said -
“Fool me once, shame on you; fool me twice, shame on me”
At this point of time,
looking at the history of “schedule discussions” on this forum,
the smart folks have stopped asking for ETAs.
“Soon” is a meme on this forum that regulars understand.
It has been proven time and time again on this forum that folks who provide estimated schedules lack the confidence / discipline / (whatever other reasons/incentives that prevent them from calmly stating -
“Sorry, cannot promise anything, will update once we have something to share”,
and adding the link to the topic-thread to their internal task-tracker
for them to provide an announcement update and a comment with the link to it in each of the topic-threads, once the task in complete.)
If enough people ask for an estimated schedule,
they WILL eventually share some timeline
without emphasizing that it is only an estimate and not a promise. 
To their credit, judging by the evolving pattern of comments over the years, it appears that they have been asked to avoid sharing estimates, and they do try to avoid sharing estimates to the best of their abilities. But, once in a while, presumably when they are unusually confident about their ongoing tasks, they do slip-up and share an estimated schedule - only to encounter unforeseen challenges, and end-up disappointing themselves and anyone else who was naive enough to rely on them as deadlines.
Everyone please stop with this naivete. 
Instead maybe (just maybe) if we all demonstrate some maturity to differentiate between a roadmap and a contract (both when asking for and answering about estimated schedules) we might be able to have more meaningful conversations.
If you are one of the folks who has been caught in such a situation of having shared an estimated schedule on this forum that was inevitable revised, Please review your social-media training on how to collect user-feedback and provide timelines without setting unrealistic expectations. If you aren’t aware of such a training, maybe ask your team/org leaders to create one and share it within the team/org.