Spot on. Each time Drupal build another release I have to consider the opportunities created by upgrading to their latest release versus the pain caused in upgrading, which largely means...
1. discovering what modifications have been made between the current version and the upgrade (I only do this, so that if the upgrade goes pear-shaped, I know where to start looking to fix it.)
2. understanding the upgrade path.... can I upgrade from 4.1 to 4.6 or do I need to follow an upgrade path, 4.1 --> 4.2 --> 4.3
3. reminding myself, what customisations have I made to the core code, so that I can re-apply those changes after the upgrade.
4. having the courage to fix what ain't broken.
Your comments spur me on to write a series of posts on 'the problem with open source'
Jonathan
Spot on. Each time Drupal build another release I have to consider the opportunities created by upgrading to their latest release versus the pain caused in upgrading, which largely means...
1. discovering what modifications have been made between the current version and the upgrade (I only do this, so that if the upgrade goes pear-shaped, I know where to start looking to fix it.)
2. understanding the upgrade path.... can I upgrade from 4.1 to 4.6 or do I need to follow an upgrade path, 4.1 --> 4.2 --> 4.3
3. reminding myself, what customisations have I made to the core code, so that I can re-apply those changes after the upgrade.
4. having the courage to fix what ain't broken.
Your comments spur me on to write a series of posts on 'the problem with open source'