Difference between revisions of "Steps for a patch release"

From OpenEMR Project Wiki
Line 5: Line 5:
:3. Build a zip file of all files that have been modified in rel-410 (since the official 4.1 release)
:3. Build a zip file of all files that have been modified in rel-410 (since the official 4.1 release)
:4. Release the zip file
:4. Release the zip file
::*Place in 'Patches' tracker on sourceforge with description (attach the zip patch file there)
::*Place in 'Patches' tracker on sourceforge with description (Attach the zip patch file there; if file is too big (over 256 kb), then place it in the patch directory on the open-emr.org website and place a link to this in the tracker item.)
::*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 and on the [[OpenEMR_Twitter_Feed|Twitter Feed]], on the [[OpenEMR_Facebook_Page|Facebook]] page, and on the [[Google_Plus|Google+]] page.
::*Announce the release in the forums and on the [[OpenEMR_Twitter_Feed|Twitter Feed]], on the [[OpenEMR_Facebook_Page|Facebook]] page, and on the [[Google_Plus|Google+]] page.


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

Revision as of 21:58, 25 November 2011

Steps detailing a patch release (using rel-410 (version 4.1) is given as an example):

1. Ensure the database changes have been added to the sql/patch.sql 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-410 (since the official 4.1 release)
4. Release the zip file
  • Place in 'Patches' tracker on sourceforge with description (Attach the zip patch file there; if file is too big (over 256 kb), then place it in the patch directory on the open-emr.org website and place a link to this in the tracker item.)
  • On the OpenEMR Patches download page, place the description and a link to the patch file.
  • Announce the release in the forums and on the Twitter Feed, on the Facebook page, and on the Google+ page.