Difference between revisions of "Patch Mechanism"
From OpenEMR Project Wiki
Bradymiller (talk | contribs) (Created page with "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,...") |
Bradymiller (talk | contribs) |
||
| Line 1: | Line 1: | ||
Note this page is for developers to describe the patch process. For Patches go to the [[OpenEMR Patches]] wiki page. | |||
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 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. | ||
In future, planning to also incorporate a mechanism (sql_patch.php) to allow modifications of the database. | In future, planning to also incorporate a mechanism (sql_patch.php) to allow modifications of the database. | ||
Revision as of 23:03, 14 October 2011
Note this page is for developers to describe the patch process. For Patches go to the OpenEMR Patches wiki page.
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.
In future, planning to also incorporate a mechanism (sql_patch.php) to allow modifications of the database.
