Difference between revisions of "Steps for a patch release"

From OpenEMR Project Wiki
 
(18 intermediate revisions by the same user not shown)
Line 1: Line 1:
Steps detailing a patch release (using rel-502 (version 5.0.2) is given as an example):
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)
: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
: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-600 (since the official 6.0.0 release)
: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. Release the zip file
:4. Place the git tag (example v7_0_3_3) on github repo: 'git tag v7_0_3_4 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)
::*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.
::*On the [[OpenEMR Patches]] download page, place the description and a link to the patch file.
::*Announce the release in the forums (both the patch thread and create a new thread in News), on the trackers(github and sourceforge), chats, on the [[OpenEMR_Twitter_Feed|Twitter Feed]], on the [[OpenEMR_Facebook_Page|Facebook]] page, on the [[OpenEMR_Diaspora_Page|Diaspora]], on the [[OpenEMR Mastodon Page|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.
::*Announce the release in the forums (create a new thread in News), chats, on the [[OpenEMR_Twitter_Feed|Twitter Feed]], on the [[OpenEMR_Facebook_Page|Facebook]] page, on the [[OpenEMR_Diaspora_Page|Diaspora]], on the [[OpenEMR Mastodon Page|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 tags (patch and patch/date tags) for the patch version in the github action file.
:7. Update the Release History on main wiki page
:8. Point the demo farm production docker to the new tag


[[Category:Patch]][[Category:Release]]
[[Category:Patch]][[Category:Release]]

Latest revision as of 22:53, 18 May 2025

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_4 rel-703'
5. Release the zip file and the docker
6. Build/release the docker. Ensure update tags (patch and patch/date tags) for the patch version in the github action file.
7. Update the Release History on main wiki page
8. Point the demo farm production docker to the new tag
Retrieved from "https://www.open-emr.org/wiki/index.php?title=Steps_for_a_patch_release&oldid=36512"