Software tool vendors will put out new releases from time to time and when they do, the development teams that use those tools need to decide if and when to upgrade. Often, it's not convenient to upgrade as soon as the new release is available. The project may be too close to a release. There may be a high rate of bug fixes to make. Maybe there is a new major feature being developed that's taking the full attention of the developers. It's alright to wait a bit before upgrading your toolset but don't make it too long a wait. The longer you wait, the harder the upgrade becomes. I've seen projects that haven't upgraded in 15 years. They then find that upgrading becomes a multi-month project with a high risk of going over budget. Usually, the only way to perform these tool upgrades is to try it and tackle the problems that come up one by one. When you wait several releases to upgrade, the number of problems you'll encounter increases and the upgrade becomes much harder. As far as possible, try to keep up to date with the tool vendor releases.
Download