It is not necessary that upgrades are made at all. In my opinion, if its working ok then what is the need? but ofcourse there are 1 or 2 members who keep harping on about we need to upgrade from 3.0.1 to 3.0.2
and generally make me look bad about 'how I don't care' if it doesn't get done, etc etc. so eventually I think well maybe it would run better, more reliable and faster so whats the harm.
Web server software: Took several days to get it to run ok with vbulletin, database and php. Lots of downtime for everyone and lots of work for me.
PHP upgrade: Took several days to correctly get it to work with database software. = downtime
Vbulletin = a few hours downtime to upgrade, months for users to find where functions had moved to.
Database software: didn't agree with data created from previous version = crash and 1-2 days downtime.
And its still ongoing, vbulletin now tell me that this version of vb does not run well at all with the newer database software. So I need to have the latest vb and the latest database software which means another upgrade and so it goes on.........
Maybe things would run smoother if upgrades we run more frequently, so less of a jump, maybe thats a better stratergy?
So next time one of those? omg why hasn't vbulletin been upgraded to 3.0.0.0.x by now? We all now the answer.