My favorite blog template, Thesis, just announced an upgrade to version 1.6. A client asked if they should upgrade their version. I advised them to move cautiously. For my own web sites, I usually upgrade to the latest version of whatever technology I’m using, but rarely am I an early adopter. Some guidelines on upgrading:
- Don’t be the first to try it out – unless you already have problems or time on your hands. Even the best vendors and technology will have bugs – let someone else find them for you. Wait a few weeks until patches are provided. If you aren’t sure the status of an upgrade, check the support forum and see how many unresolved issues remain.
- If it’s not broke, don’t fix it. Unless you have issues or problems with a piece of technology, don’t rush to upgrade.
- Make sure you need or even want the upgrade. Must upgrades offer new features – make sure they are worth the effort.
- There is always a chance you’ll break something in the upgrade – do you have the time to fix it if it breaks? If you don’t, you might want to pay someone who has significant experience with the item and let them work through the issues.
- Backup Early and Backup often – if #4 comes to pass, at least you can roll back to a version that works.
- Test everything – the strangest things tend to stop working when you upgrade. Test all the modules, links and other add-ons. If it is a web site, look at every page – a single wayward piece of code can wreak havoc on content and format. If you are pressed for time, test the most complex items first– they are the most susceptible to breaking.
There are no points awarded for being the first to upgrade, but there may be some substantial penalties for rushing in.
