When I initially started keeping track of my upgrades, of both WordPress but also mostly all other software updates as well, it was since there had been several bugs caused by updates, in turn causing me to spend a lot of time troubleshooting and resolving these. And I wanted to keep a log on when I upgraded, what I upgraded to easier find and resolve issues and how much time I spent on these rather meaningless tasks.
Over the last few years the updates on all platforms I use have both become so frequent it’s become quite impossible to write them all down, the steady trickle of updates have become a huge flood, but on the other hand updates have overall, with some quite notable exceptions, become much better in quality and have required less and less time and intervention from me.
Such as with WordPress, which has been silently and robustly updating itself across all my sites. With an exception today, where the 4.9.4 update just sat there waiting for my approval, for some reason. Maybe I was too fast, or just logged in precisely at the time it became available and the auto-update had not yet had time to react, I don’t know, but there it was, the surprise of having to manually initiate an update. But it worked flawlessly.
The danger of all these successful auto-updates is that I’ve been negligent with doing backups. Since they usually work. And usually update themselves overnight. And doing backups “just in case” is a really great example of wasting time which I don’t have.
Anyway, if only MediaWiki could advance to a state where updates could be performed with the same ease as WordPress. Since at the moment leaving MediaWiki is not an option.
And the cumulative updates of Windows 10 and Windows server are still a pain in size and time taken to install, even if they auto-update fairly well most of the time…