Hm, to be a little bit more precise PIH is syncing in Haiti, Rwanda, and Malawi.

In Malawi we are on 1.7.2 and I don't see us upgrading soon. However, we live 
with this logging 'feature' since about a year, so I don't see the need to just 
branch for this. I guess the problem will arise if sync requires 1.8 and there 
are additional features/bugfixes that we need. I'm willing to deal with this 
once we have this situation.

Off-topic: Our usage of 'short living' child servers might help us as well. We 
don't rely on sync and the interceptors that much as we frequently 
re-initialize the child servers and can still do data manipulation/correction 
on the DB level (more similar to the RemoteFormEntry approach). This way our 
dependency to sync isn't that high and we only depend on it for the way back 
from the child to the parent server for patient data (like Encounter, Obs, 
Identifiers, ...). Metadata and other configurational parts are not supposed to 
be sync'ed.

christian

On Sep 29, 2011, at 4:04 PM, Mark Goodrich wrote:

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]> [mailto:[email protected]] On 
Behalf Of Michael Seaton
Sent: Thursday, September 29, 2011 8:48 AM
To: 
[email protected]<mailto:[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
________________________________
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]

Reply via email to