DHIS2 release cadence
The DHIS2 core team typically releases a new major release version two times per year. Support from the core team extends to the three most recent DHIS2 versions. For example, if 2.39 is the latest release version, the DHIS2 core team will provide support and updates for 2.37, 2.38, and 2.39. BAO Systems strongly encourages our clients to stay up to date with the latest DHIS2 version or a subsequent version that is still officially supported. Staying current and supported is especially important for security - if you do not stay on a current version, then we cannot apply security patches released by the DHIS2 core team, leaving your system, and your data, vulnerable to attack. Please see the official DHIS2 roadmap.
Upgrade process
BAO Systems creates a backup of your database prior to every upgrade and performs the upgrade on your behalf. If we encounter critical errors during the upgrade process, we will attempt to solve them quickly. If this is not possible, we will roll back and contact you with details to determine next steps.
Testing prior to upgrading production instances
BAO Systems evaluates all stable releases for compatibility with our systems. However, it is still important that you test new releases against your actual production DHIS2 database to ensure that all works as expected.
We recommend copying your production database to a non-production environment to fully vet all upgrades before deploying a new DHIS2 version to your production environment. Many of our clients maintain test environments that are hosted by BAO Systems. Plan to test data entry, reports, SQL views, custom apps, Android apps and any scripts or tools you use to connect to the API, including downstream reporting systems, as well as any other components critical to successful operation of your implementation. If you have a DHIS2 support plan with BAO Systems, you have the option of engaging with our team should you require assistance testing or developing a test plan.
If you are unable to utilize a test environment hosted by BAO Systems, we encourage you to download a recent backup of your production database from BAO Manager and test the upgrade on your own premises. BAO Systems does not provide support for your on-premise instances.
If you are unable to test in a test environment, we can upgrade your production instance with the understanding that, should you require a rollback, you would lose any changes made to the database since the upgrade was performed.
Scheduling your upgrade
Once you've thoroughly tested the upgrade, our team will work with you to schedule a time during our normal business hours to perform the upgrade in your production environment.
Rollback limitations
It is not possible to roll back a DHIS2 database to a previous version. For example, if you upgrade from 2.37 to 2.38 and discover a critical issue with your implementation under 2.38, you would need to roll back the database to the 2.37 backup we took prior to the upgrade. This means that you would lose any changes to the data or structure made after the upgrade—it is very important to test thoroughly!
Performance expectations
As DHIS2 matures and new features are added, you may notice that your old hosting plan is not as performant over time due to increased resource requirements of the DHIS2 application. This may be especially true when moving from a very old version of DHIS2 to a newer release. If you notice that DHIS2 does not perform well after a recent upgrade, BAO Systems may recommend a hosting plan upgrade to ensure your implementation has sufficient resources.