I'm fine if we don't backport... as Mike said, we are planning on upgrading soon, and I'm not particularly annoyed by them. I'll let others weight in, however... Mark
From: [email protected] [mailto:[email protected]] On Behalf Of Michael Seaton Sent: Thursday, September 29, 2011 8:48 AM To: [email protected] Subject: Re: [OPENMRS-DEV] Sync OpenMRS version requirement PIH is using sync in production in both Haiti and Rwanda, both currently running 1.6, both planning to upgrade to 1.8 within the next month or so if all goes according to plan. On 09/29/2011 07:52 AM, Ben Wolfe wrote: The Sync Module currently works all the way back to OpenMRS 1.6.2. However, there is a "feature" that the SyncService.shouldSynchronize method logs something every time something is saved. This can be fixed if the module is set to require OpenMRS 1.8. Unfortunately this would mean branching the sync module and backporting any features to a second codebase every time. I want to avoid this for as long as possible. How many sync users are out there on pre 1.8 ? (I know PIH in Rwanda is, but they are upgrading to 1.8 very soon) Or how many sync users see that extra logging as annoying enough that we should start the branching? Ben ________________________________ Click here to unsubscribe<mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> from OpenMRS Developers' mailing list ________________________________ Click here to unsubscribe<mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> from OpenMRS Developers' mailing list _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
