Perfect. Thanks.
Regards
Vanya
On Mon, Sep 26, 2016 at 1:20 PM, Lars Helge Øverland wrote:
>
> Thanks. Yes we will definitely check it out.
>
> Lars
>
> On Mon, Sep 26, 2016 at 9:47 AM, Vanya Seth
> wrote:
>
>> Hi Lars
>>
>> Sure. This feature we can
Thanks. Yes we will definitely check it out.
Lars
On Mon, Sep 26, 2016 at 9:47 AM, Vanya Seth wrote:
> Hi Lars
>
> Sure. This feature we can target for 2.26. But the other PR's that we will
> send today you would consider them for 2.25 ?
>
> Regards
> Vanya
>
> On Mon,
Hi Lars
Sure. This feature we can target for 2.26. But the other PR's that we will
send today you would consider them for 2.25 ?
Regards
Vanya
On Mon, Sep 26, 2016 at 1:11 PM, Lars Helge Øverland wrote:
> Hi Vanya, we are having a code freeze tomorrow so that might be a bit
>
Hi Vanya, we are having a code freeze tomorrow so that might be a bit late.
Would be great if we can target this for 2.26.
best regards,
Lars
On Mon, Sep 26, 2016 at 7:28 AM, Vanya Seth wrote:
> Thanks for the information.
>
> Could you also tell about the release
Thanks for the information.
Could you also tell about the release timeline for 2.25? If we plan to do
this for 2.25 then whats the time frame that we are looking at?
Regards
Vanya
On Sat, Sep 24, 2016 at 5:58 PM, Lars Helge Øverland wrote:
> Hi Vanya,
>
> yes this sounds like
Hi Vanya,
yes this sounds like a good idea to me. Of course, if the metadata is in
fact compatible it is unnecessary to abort, but since we do not have a
solid way to define which DHIS 2 versions are metadata compatible I think
this could be a good idea. Please go ahead.
best regards,
Lars
On
Hello Lars and Morten
We are considering adding another feature to the metadata sync and
versioning.
The idea is to stop sync if the Remote server (Central instance) and the
field instance are on different DHIS2 versions. This is important as
metadata created on one version of DHIS2 might not
7 matches
Mail list logo