DHIS2 patch release 2.36.9 is now available - HOTFIX

Dear all,

DHIS2 version 2.36.9 (patch release) is out as a HOTFIX release to address Jira issue DHIS2-12182.

This is the latest stable release for version 2.36, and supersedes releases 2.36.0 to 2.36.8.

The release note for this patch can be found here: Patch 2.36.9 Release Note.

Thanks!

DHIS2 Release Team

Release Information Links
Release Note Patch 2.36.9 Release Note
Upgrade notes 2.36 Upgrade notes
Download release and sample database Downloads - DHIS2
Documentation and Javadocs Home - DHIS2 Documentation
Source code on Github Release 2.36.9 · dhis2/dhis2-core · GitHub
Demo instance DHIS 2 Demo - Sierra Leone
Docker docker pull dhis2/core:2.36.9
for more docker image variants see dockerhub
4 Likes

Hi @phil
Thanks for this release. We were expecting this release to include a fix for data visualization of certain indicators. The fix was done on master (fix: DataHandler visualizations fix DHIS2-12518 by jimgrace · Pull Request #9720 · dhis2/dhis2-core · GitHub) at the end of January and backported to 2.36 on Feb 1st (fix: DataHandler visualizations fix DHIS2-12518 (#9720) by jimgrace · Pull Request #9732 · dhis2/dhis2-core · GitHub) but the code has never reached a release if I am not wrong. This code is particularly critical for some of our clients as it fixes several visualizations that show up as empty. Is there any reason why this commit didn’t make it to 2.36.9? Can we expect it to be included into 2.36.10? Many thanks!

2 Likes

Hi @adrianquintana,

This release is a particular type that we call a HOTFIX. These are special releases that we make to fix specific critical issues. We make the release by taking the previous version and applying only the target fix or fixes; allowing us to release quickly and with low risk.

As a consequence, HOTFIXES cause all of the fixes that are ready for the “next” patch, to be bumped to the subsequent patch. In your case, yes, DHIS2-12518 will now be included in 2.36.10.

Note that HOTFIXES don’t change the timeline for nominal fixes to get into the next patches. For example, if we had not released 2.36.9 as a HOTFIX, then it would not be released yet, but would be released some time in late April. Therefore, 2.36.10 should now be released in late April - when 2.36.9 would have been released (if we had no HOTFIX).

Kind regards,
Phil

2 Likes

Thanks for your quick reply @phil. Understood! We will wait for the release in late April to get this fixed. Just one final question, where can we find the estimated release date for future versions? We were browsing around in Jira (Log in - DHIS 2 JIRA) but couldn’t find that information.

Hi @adrianquintana,

If you mean release date for patches, we deliberately don’t publish our target dates as they can change due to many factors. The rule of thumb is that in general we try to release the next patch approximately two months after the last. (Note that we are currently entering the final testing phase for 2.38, and we usually slow down maintenance patch releases during major releases).

For major releases, we try to stick to a more firm timeline, and you can find a clearer overview of that on our Roadmap.

Kind regards,
Phil

2 Likes