Difference between revisions of "Patch Mechanism"

From OpenEMR Project Wiki
Line 12: Line 12:


==Ongoing Patch Trails==
==Ongoing Patch Trails==
:[[Ongoing 5.0.2 Patch Trail]]
:[[Ongoing 5.0.1 Patch Trail]]
:[[Ongoing 5.0.1 Patch Trail]]
:[[Ongoing 5.0.0 Patch Trail|Prior 5.0.0 Patch Trail]]
:[[Ongoing 5.0.0 Patch Trail|Prior 5.0.0 Patch Trail]]


[[Category:Patch]][[Category:Release]][[Category:Developer Guide]]
[[Category:Patch]][[Category:Release]][[Category:Developer Guide]]

Revision as of 01:59, 6 August 2019

Note this page is for developers to describe the patch process. For actual Patches, go to the OpenEMR Patches wiki page. And for the steps on how to release a offical patch, go to the Steps for a patch release wiki page.

Patch Mechanism

This is currently rather simple and involves a step to update the codebase and a step to update the database.

Codebase

All new code is carried over to a release branch (ie. rel-xxx) and all files that have been modified are intermittently packaged in a zip file. So, can upgrade code by patching from the rel-xxx branch or by patching from the packaged zip file.

Database

The sql_patch.php script will upgrade database, globals, and the version/patch (from version.php script). It loads the database changes from the sql/patch.sql file.(note also add database changes to database.sql in case users install from the rel-xxx branch)

Ongoing Patch Trails

Ongoing 5.0.2 Patch Trail
Ongoing 5.0.1 Patch Trail
Prior 5.0.0 Patch Trail