Steps for a patch release

Steps detailing a patch release (using rel-800 (version 8.0.0.2) 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-800 (since the official 8.0.0 release). Build using the following script: https://gist.github.com/bradymiller/4f7817a7f2081891ccc93904914ea6f4

4. Place the git tag (example v8_0_0_2) on github repo: 'git tag v8_0_0_2 rel-800'

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) (then use openemr website tool within the server to import in the updated repo: `docker compose restart static-files-sync`)
• Build changelog in master via the changelog script. (php console openemr-dev:create-release-change-log -m "8.0.0.2" > changelog) (copy/paste output into CHANGELOG.md file in master branch)
• On the OpenEMR Patches download page, place the description and a link to the patch file.
• Update tags (patch and patch/date tags) for the patch version in the github action file(https://github.com/openemr/openemr-devops/blob/master/.github/workflows/build-800.yml#L28). Build/release the docker via github action. Update dockerhub readme (https://hub.docker.com/r/openemr/openemr/).
• Announce the release in the forums (create a new thread in News), chats, on the Twitter Feed, on the Facebook page, 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, and announce to registered users.

6. Update the Release History section on main wiki page

7. Point the demo farm production docker to the new tag here in this file. Note the demo resets every night. Can manually reset it via the admin controller gui.