In reply to Central Geek.

Thank you for pointing out the obvious. However, this is delving into another subject. The flaw in all of the logic is that forced automatic updates should be happening when apparently nobody understands fully the impact of changes to the thousands of lines of code which apparently are NOT adequately documented.

And that is where I return to this topic and call for either an option to turn "on" automatic updates or abandon the requirement altogether until more adequate documentation is available for not only those who extend WordPress, but those who are contributing to a core nobody really has a full understanding of.

Again, thanks for the invitation. But again, I believe the core developers and the core contributors need to STOP, take a STEP BACK and AUDIT WordPress code and fully document so that there is better understanding of what impact these updates have on plugins as well as unsuspecting websites.

I have been seeing a lot about "security". What exactly is security when nobody fully understands the code contained in the project?

Thanks