It would be nice to share these implementation issues on the implementers list. We've asked the AMPATH team to do so.
-Burke On Tuesday, August 2, 2011, Ben Wolfe <[email protected]> wrote: > I was only around as a backup, and didn't get any calls until testing > things the next day. They started it Friday at 7pm and it was done by > Sunday at 2pm. > > Nothing failed in the changesets during the upgrade that I know of. > There were some bugs found after starting around formentry that will > require some programming fixes. Temporary hacks are in place for now. > > I'll have one of the AMPATH devs reply in case I'm misrepresenting the process. > > Ben > > On Tue, Aug 2, 2011 at 2:11 PM, Dave Thomas <[email protected]> wrote: >> hey ben. i'd be curious to hear how it went. were the difficulties mostly >> around having each changset take 9 hrs to run? did you discover anything >> that required manual cleanup to complete the process? >> d >> >> On Tue, Aug 2, 2011 at 12:51 PM, Ben Wolfe <[email protected]> wrote: >>> >>> In light of the AMPATH project updating from 1.6.2 to 1.8.2 this past >>> weekend, I want to propose a module to ease their and other large >>> database owners' updates in the future. It would be a module that >>> allows an admin to execute arbitrary changesets from a given file >>> (like the war file they will be upgrading to). >>> >>> The idea is to allow the long-running and backwards compatible >>> changesets like index additions, column additions, etc, to be run >>> while the old application version is still in use. This way they can >>> run some changesets the few weekends before the big update to make >>> sure that the big update is actually done during the scheduled >>> downtime. >>> >>> See the project page: >>> >>> >>> https://wiki.openmrs.org/display/projects/Execute+Database+Updates+Module+%28Design+Page%29 >>> >>> Ben >>> >>> _________________________________________ >>> >>> 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] >> >> ________________________________ >> Click here to unsubscribe 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] > > _________________________________________ 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]
