Hi Dawn,
For us (HAS), fewer changes with more frequent releases would be best. Having fewer changes at a time would be beneficial for us because of the large single implementation that we run. Doing the database updates during an upgrade takes a considerable amount of time. Having that split into multiple releases over time would be favorable. Our testing consists of updating our test server with the database dump from the previous night, and deploying the war file to be tested. I prefer doing it this way as opposed to using the Release Testing Helper module and Standalone because the latter option doesn't test my environment; compatibility with my OS, Java, and Tomcat versions; the OpenMRS stand alone is also a BIG download for us. For the community, supporting a version base that includes more similar versions released in a shorter time-span would be better. It would also reduce the need to back-port as much if a new version is released more frequently, older versions would also reach EOL sooner. At the same time, we allocate a significant amount of time to testing the potential releases. Doing this more frequently would require additional resources. This is one way that we can contribute back to the community. Having a major release per our current frequency isn't bad, but slightly more frequently might be better. Thanks, James From: [email protected] [mailto:[email protected]] On Behalf Of Dawn Smith Sent: Tuesday, April 24, 2012 5:16 PM To: [email protected] Subject: [OPENMRS-IMPLEMENTERS] Full System Upgrades: How Often Should They Happen? Hi Everyone, On the recent developers forum we talked about ways in which OpenMRS has changed the road map focus from version numbers (updates to the core) to a road map focused on what's most important to implementations (features and functionality). What we envision in the long term is that implementing sites will drive the direction of development.. So as we move in this direction, what we want to know is: How often should full system upgrades happen? One of the things we also want to understand in your answer is what the overhead is for an implementation to update to a new release. This may include consideration that a roll out needs to occur over multiple sites and/or the resources and time it takes for an implementation to do thorough testing. The more information you can provide, the better! Thank you in advance for your feedback. :) All the best, -Dawn ________________________________ Click here to unsubscribe <mailto:[email protected]?body=SIGNOFF%20openmrs-implement-l> from OpenMRS Implementers' mailing list _________________________________________ To unsubscribe from OpenMRS Implementers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-implement-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-implement-l]
