dhis2-devs team mailing list archive

[Elmarie Claasen <elmarie@xxxxxxxx>]

Hi Georgi,

What we usually do is to upgrade a staging instance to latest stable war
and start testing all functionality users are using and also the config
apps. Once we determine it is stable and dont see major bugs reported and
still unresolved on Jira we upgrade.

Might be a useful approach for you to follow.

In general it depends where you upgrade from. If a much older version
before api versioning was introduced we had some issues with html reports
that had to be adapted when upgrade to 2.24 but otherwise no major issues.
If you using program rules check those are firing properly.

Elmarie

On 15 May 2017 13:12, "Georgi Chakarov" <georgi@xxxxxxxxxxxxxxxxxxx> wrote:

> Hello!
>
>
>
> Has anyone been using DHIS2 version 2.26, already? Can you confirm that it
> is steady and the apps work good?
>
>
>
> In general, how and where can I check whether a higher version of DHIS2 is
> stable?
>
>
>
> Thanks in advance for your input on this!
>
>
>
> Georgi
>
>
>
>
> Georgi Chakarov, CIA | georgi@xxxxxxxxxxxxxxxxxxx | +1-647-478-5634 x 104
> <(647)%20478-5634> | LogicalOutcomes c/o Centre for Social Innovation,
> 720 Bathurst Street, Toronto Canada M5S 2R4 | *You may unsubscribe from
> receiving commercial electronic messages from LogicalOutcomes by emailing *
> *info@xxxxxxxxxxxxxxxxxxx* <info@xxxxxxxxxxxxxxxxxxx>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-users
> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>

-- 


*This message and any attachments are subject to a disclaimer published at 
http://www.hisp.org/policies.html#comms_disclaimer 
<http://www.hisp.org/policies.html#comms_disclaimer>.  Please read the 
disclaimer before opening any attachment or taking any other action in 
terms of this electronic transmission.  If you cannot access the 
disclaimer, kindly send an email to disclaimer@xxxxxxxx 
<disclaimer@xxxxxxxx> and a copy will be provided to you. By replying to 
this e-mail or opening any attachment you agree to be bound by the 
provisions of the disclaimer.*