I think I agree with you for discrete product releases, but for ongoing SaaS and moreso PaaS, it's helpful for integrations to have some visibility on your roadmap. I'm might just write a hack workaround for some issue if I have a belief that in 2024 you'll solve X -- I've got bigger fish to fry. But if I know you've removed it from your roadmap and it was planned by me, I can put it on mine to resolve. Surprising me with features means more often than I care to admit I write something to solve a problem, use it for a few months, and then vendor comes out with a solution to it that's close enough and better supported so I toss out code -- with a roadmap I could have avoided overlapping efforts.

But I'm more on the operational side - so I care more than most about the integrations with lots of vendors, different PoV's may of course differ.

I feel you. You seem to be reasonable and empathetic and understand that sometimes priorities change and that an imperfect roadmap can still bring benefits over a hidden one. On the other hand, there are a lot of people who feel entitled to get anything you ever mentioned, even (especially) if they’re getting it for free, and managing those people when they complain is time consuming and drains your sanity. Both of which take your time and energy away from improving the product to all the reasonable people.