Upgrades

We plan two comprehensive upgrades per year for all of our clients. We ask them to budget for between 2 and 4 upgrades as security releases may be required in between planned upgrades.

By comprehensive upgrade, we mean upgrading all of the following components to the latest compatible version:

• CiviCRM
• CiviCRM extensions
• the CMS (typically WordPress)
• any CMS plugins, themes and modules
• PHP

In some instances we may choose to hold back one of more of the above components, due to known bugs or incompatibilities.

Whenever possible we upgrade all clients at the same time. This is to ensure that, wherever possible, all clients are using the same versions of software, which makes it easier to support them. But there may be exceptions to this rule, for example, if a particular client needs a newly released feature, we may choose to upgrade them earlier than others.

We may sometimes choose a different month than the default month. This could happen, for example if we have recently upgraded a site due to a security release.

In this section of the handbook, you can read about the upgrade process, security releases and dealing with core and extension overrides. We predominantly track time spent on upgrades initially under the client wide project, and then redistribute that time across the clients who it affected before we invoice. Any specific upgrade work we do for a particular client can be tracked directly under that client project.