Steps for a patch release
From OpenEMR Project Wiki
Revision as of 08:50, 18 May 2025 by Bradymiller (talk | contribs)
Steps detailing a patch release (using rel-703 (version 7.0.3) is given as an example):
- 1. Ensure the database changes have been added to the sql/patch.sql(and database.sql for new installs) file (and tests that it works)
- 2. Increment the $v_realpatch variable in the version.php file
- 3. Build a zip file of all files that have been modified in rel-703 (since the official 7.0.3 release). Build using the following script: https://gist.github.com/bradymiller/4f7817a7f2081891ccc93904914ea6f4
- 4. Place the git tag (example v7_0_3_3) on github repo: 'git tag v7_0_3_3 rel-703'
- 5. Release the zip file and the docker
- Place it in the patch directory on the open-emr.org website (https://github.com/openemr/website-openemr-files)
- Build changelog in master via the changelog script.
- On the OpenEMR Patches download page, place the description and a link to the patch file.
- Announce the release in the forums (create a new thread in News), chats, on the Twitter Feed, on the Facebook page, on the Diaspora, on the Mastodon, on the LinkedIn OpenEMR group at https://www.linkedin.com/groups/13589019, LinkedIn OpenEMR company page at https://www.linkedin.com/company/28995910, reddit openemr group at https://www.reddit.com/r/OpenEMR, Hacker News, and announce to registered users.
- 6. Build/release the docker. Ensure update tag for the patch version in the github action file.
- 7. Update the Release History on main wiki page
