How to Join
Click here to expand...
By Browser
By telephone
- US telephone number: +1 201.479.2627
Agenda
- Quickly review previous meeting minutes (5 min)
- Release Process
- OpenMRS 1.11
- After-action review & next week's agenda (5 min)
In Attendance
Minutes
View at notes.openmrs.org
OpenMRS Developers Forum: 2013-04-03
Attendees
Agenda & Minutes
- TODO: Burke will get PIH presentation from Mike Seaton added to the wiki page
- TODO: Burke & Darius to clean Road Map up
- TODO: Send out an e-mail announcement to dev@ & implementers@ informing people about the new project. (Elliott)
- Reviewing the current release process
- Timing of releases (i.e., setting some goals)
- We never want to go more than a year between releases
- Releasing an update (minor or major) to our reference application at least twice a year
- Marchs & Septembers (e.g., merge code in Jan & July)
- Releasing an update (minor or major) to our platform application at least once a year
- Septembers (e.g., merge code in July)
- When do we set "the date" for a release? Feature-driven or time-driven... or compromise?
- We'll try time-based in the 2014-2015
- Recipe for releasing (being a release manager)
- Why isn't anybody taking notes here?
- Need to consider separate release process page for reference application vs. platform?
- Need more automated tests for OpenMRS 2.0
- TODO: Testing discussion in dev forum
- Need to get basic release testing automated & sustainable
- Still just taking notes by myself. /me wishes we were better at taking notes during meetings.
- s/etherpad/wiki/g (note that Burke has been better about copying & pasting notes into wiki after meetings)
- TODO: We need to find way(s) to encourage implementations to help test new releases
- What things could make it worthwhile? Are there any incentives?
- Release Testing Module was a good idea, but was stopped b/c of issues with getting module-specific data transferred.
- Could modules support a testing interface (getTestData & saveTestData)?
- Are there out-of-the-box approaches we could take to encourage testing?
- Can we create demo sites with different combinations of modules?
- We currently have 1 system for UAT on order and more can be obtained.
- Plan on ordering 72 of them.
- Ok. We can settle for 30.
- Mike has built some pretty cool tools for exporting random/helpful subsets of data, deidentifying them, etc. There was also a SoC project about this sort of thing. => If OpenMRS can set up a hosted server with all the relevant modules, and we just need to get one implementation to send us realistic testing data.
- TODO: really could use a realistic demo data set – i.e., great to have the tools, but where are the de-identified data?
- Implementations probably feel more comfortable giving deidentified test data with limited access, just to the implementation itself plus 1-2 trusted OpenMRS devs/testers.
- Contrived test data is safe for crowdsourced testing
- Try to apply the "distribution" approach to testing releases. I.e. if an implementation tells us their modules + versions, and gives us their global properties and MDS packages of all metadata, we should be able to build a "testing distro", that can be quickly deployed by vagrant and/or other tooling.
- What does this mean as OpenMRS Platform diverges from OpenMRS 2.x?
- OpenMRS 2.0 – our reference application
- OpenMRS Platform 1.10 – API with web layer including REST (for now still has remnants of old ref app)
- Platform will be WAR + REST Web Services module
- What did you expect to happen?
TODOs
Transcripts
- Backchannel IRC transcript
- Audio recording of the call: Listen online or download - available after the meeting