In reply to Foliovision.

I’ll just add a quick note that’s off topic.

with Automattic/Wordpress.org.

It's just WordPress.org. ;) Automattic isn't WordPress.ORG. It's not word play; they do provide a great many resources and people but continuing to conflate them as the same thing just isn't true.

Long term stability and security are very important for publishers and businesses. The constant major update train is no way to run a non-technology related business.

I've added emphasis to the quote. There is a business, but it's not WordPress. If you are a paid WordPress developer or consultant and you are responsible for your customers sites and you feel that minor point revisions will negatively impact those sites then take disable auto updates. While I never recommend that, it’s an easy option to implement.

If you do take that option then you’re also taking the responsibility if and when that customer site gets compromised due to an exploit in the wild. Also there’s the impact to the rest of the Internet. Auto updates were implemented because many users were not maintaining their vulnerable code. That was ruining the whole neighborhood and contributed to WordPress having an undeserved bad security reputation.

WordPress updates are important and always get implemented in good faith to benefit the majority. Visit https://make.wordpress.org/core/ and read the #core Slack transcripts. There’s no draconian agenda here, just good people trying to make it all better.

Yes, that sometimes causes problems for some, but what’s a good percentage for successful patching? Realistically, a 100% success rate without breaking anything anywhere won’t be achievable.