Release:
We’ve cut the 8.1.0 branch, and are not intending to release any more patches on 8.0.0. Should begin testing on this branch, We may want to update more in the release-cutting script that are still parts of manual processes. Docker build has been unreliable, especually for multi-architecture setup (x86 vs arm); this may get alleviated as we make other previously-discussed improvements.
Who actually does the testing on the release (RC?) branch? We make some high-level requests on the forums. Got a suggestion to do an email blast to request additional testing.
Ref QA and Release Process - OpenEMR Project Wiki and Steps for an official release - OpenEMR Project Wiki
Iterate releases in non-dry-run on a 0.0.0patch or something?
General:
More “running OpenEMR best practices” work should occur - backups, encryption, job scheduling, etc. Minimize reliance on custom AMI builds - can we leverage other packaging here? Can more of this move into CLI tooling?
ONC certification - discussion on detection module, what % of users/etc even care? Smaller practices may not have to follow the same requirements.
Telemetry - nothing super specific, but there’s a general agreement that improving telemetry ought to make it easier and more effective to evolve OpenEMR in an informed way.
Multi-site: substantial discussion about the future of multisite and whether it makes sense to continue supporting it. Consensus is that we’re open to deprecating and removing it, but want to get more community feedback before making a firm decision. The new front-controller+DI setup will (most likely) not support it from the get-go, but may change if it turns out there are many people depending on it. We want to add info about multisite into existing telemetry.
Next meeting:
- Release (evergreen)
Please reply if you have an agenda topic you want to bring up!