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 <van...@thoughtworks.com> wrote: > 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 <l...@dhis2.org> > wrote: > >> 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 Tue, Sep 6, 2016 at 1:39 PM, Suresh Jaydev Kurumeti < >> skuru...@thoughtworks.com> wrote: >> >>> Where do we stand on this with priority for Implementation 1? >>> >>> On Tue, Aug 30, 2016 at 3:58 PM, Suresh Jaydev Kurumeti < >>> skuru...@thoughtworks.com> wrote: >>> >>>> Hi Lars, Morten, Let us know your inputs / Priority of this new >>>> feature. This would enable us plan our Implementation 1 work. >>>> >>>> On Fri, Aug 26, 2016 at 10:20 AM, Vanya Seth <van...@thoughtworks.com> >>>> wrote: >>>> >>>>> >>>>> 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 be compatible with >>>>> another version of DHIS2. This also ensures that instances tied up in this >>>>> ecosystem remain on the same DHIS2 version. >>>>> >>>>> We would like to make this change from the following standpoint: >>>>> >>>>> - Synchronization API /api/metadata/sync : spitting out relevant >>>>> http status code and message. >>>>> >>>>> - Metadata synchronization task: The task will send out an email >>>>> notification to the admin telling the reason of abort of sync. >>>>> >>>>> Please let us know how you feel about this feature (read restriction >>>>> :) ). >>>>> >>>>> We will be happy to pick it up as you give us a good to go! >>>>> >>>>> -- >>>>> With Regards >>>>> Vanya >>>>> ThoughtWorks Technologies >>>>> Hyderabad >>>>> >>>>> --Stay Hungry Stay Foolish!! >>>>> >>>> >>>> >>>> >>>> -- >>>> *Suresh Jaydev kurumetiemailskuru...@thoughtworks.com >>>> <skuru...@thoughtworks.com>Telephone+91 99018 99344 >>>> <+91+99018+99344>[image: ThoughtWorks] >>>> <http://www.thoughtworks.com/?utm_campaign=suresh-jaydev%20kurumeti-signature&utm_medium=email&utm_source=thoughtworks-email-signature-generator>* >>>> >>> >>> >>> >>> -- >>> *Suresh Jaydev kurumetiemailskuru...@thoughtworks.com >>> <skuru...@thoughtworks.com>Telephone+91 99018 99344 >>> <+91+99018+99344>[image: ThoughtWorks] >>> <http://www.thoughtworks.com/?utm_campaign=suresh-jaydev%20kurumeti-signature&utm_medium=email&utm_source=thoughtworks-email-signature-generator>* >>> >> >> >> >> -- >> Lars Helge Øverland >> Lead developer, DHIS 2 >> University of Oslo >> Skype: larshelgeoverland >> l...@dhis2.org >> http://www.dhis2.org <https://www.dhis2.org/> >> >> > > > -- > With Regards > ThoughtWorks Technologies > Hyderabad > > --Stay Hungry Stay Foolish!! > -- Lars Helge Øverland Lead developer, DHIS 2 University of Oslo Skype: larshelgeoverland l...@dhis2.org http://www.dhis2.org <https://www.dhis2.org/>
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : dhis2-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
