Ah, I see people are comfortable with lack of accountability within other software industries. Sad to see, but here we are.
You say customers still buy/use <x> product and are happy...are you sure? Have you actually done an analysis of new customers/revenue coming in vs. customers leaving and root cause? Perhaps they only buy your product because their is no other competitive option? Are you comfortable with leaving <y> profit off the table because of that problem not being addressed?
Back to RoM specifically and keeps being brought up within this thread:
If they promised a new enhancement the next day and it didn't work for <z> reason. Why wasn't <z> problem addressed earlier? Wouldn't it still be in the patch notes the next day anyways?
So many excuses occur as a result of bad planning. Sure, something very unexpected might come up, but that is what contingency plans are for.
Honestly, to be so blunt here. It sounds like you've
never been involved with ANY development projects. If you did, then you should know that software changes sometimes from system to system, and from installation to installation. Surely you would know that no two machines were created equally. What worked on my Windows 7 machine may not work on your Windows 8 machine. Likewise, what works on a test server with 30 accounts and 5 users on in a typical test environment may not work on a server that has several thousand, if not hundreds of thousands of accounts and a couple hundred users online at once.
Honestly, I'd rather the patch notes explain exactly what changed hours after the patch is released rather than know two days ahead of time what might be changed and then be disappointed and have people yelling on the forums because something wasn't able to be solved during patch time and therefore got recalled. If I recall right Frogster used to do that, probably got tired of dealing with the complaints about it all the time.