Difference between revisions of "Patch Mechanism"

From OpenEMR Project Wiki
Line 2: Line 2:




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


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


In future, planning to also incorporate a mechanism (sql_patch.php) to allow modifications of the database.
==Database==
 
The sql_patch.php script will upgrade database, globals, and the version (from version.php script). It loads the database changes from the sql/patch.sql file.

Revision as of 02:40, 15 October 2011

Note this page is for developers to describe the patch process. For actual Patches, go to the OpenEMR Patches wiki page.


This is currently rather simple.

Codebase

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

Database

The sql_patch.php script will upgrade database, globals, and the version (from version.php script). It loads the database changes from the sql/patch.sql file.