When should I update an Inedo Tool?

KB#1059: Last Updated January 3, 2020

Updating any software to a newer version requires users to weigh the costs associated with the update process against the value and benefits of the new features or bug fixes added – and this is no different with any of our tools. As a DevOps company, we take great care to design and release our tools through a process that permits a super-agile deployment methodology. Which allows many releases to occur in a short time frame.

In order to help ease the update process, we have three types of releases has the following special considerations.

Maintenance Updates (e.g. 3.5.7 to 3.5.8)

Maintenance releases are low risk and contain only backwards-compatible enhancements, bug fixes, and security patches.

Individual changes are carefully documented on our public issue tracker and follow our rigourous Change Management Process. Users may even request source code access to see exactly what changed.

However, lots of small, low-risk changes add up over time, so we recommend updating at least once per quarter to minimize the risk of a regression.

Major Updates (3.1 to 3.2, or 4.5 to 5.0)

A major release typically implements a brand new feature or overhauls an existing one, and may introduce:

  • backwards-incompatible API changes
  • SDK changes that may require custom extensions to be recompiled
  • major database schema changes
  • major UX changes
  • major functionality updates
  • all bug fixes up to and including the new major version

Because of the major changes that may be introduced, you should always carefully read the upgrade notes if you do not do so already before performing a major update.

In most cases, you should schedule a specific time-slot away from crucial deployments in order to perform a major update. Many users even setup separate instances in order to explore functionality before rolling out the update to their production instance.