Difference between revisions of "Steps for an official release"
From OpenEMR Project Wiki
Bradymiller (talk | contribs) |
Bradymiller (talk | contribs) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
==1. Create a rel-??? branch from master in the git repo.== | |||
==2. Release an online development demo that uses the rel-??? branch and updates daily.== | |||
==3. Publish installation, upgrade, and downloading instructions== | |||
:*Also provide links for downloading rel-??? packages to allow testing of installation and upgrading by testers | |||
==3. Finalize the translations in the rel-??? branch.== | |||
==4. Bug fix and finalize the rel-??? branch.== | |||
==5. Create a list of new features in the rel-??? branch (since the last official release)== | |||
==6. Release rel-??? branch by tagging in git repo with v?_?_?.== | |||
::* Things to remember before tagging the release. | ::* Things to remember before tagging the release. | ||
:::* Remove dev (make it blank) from the version.php file | :::* Remove dev (make it blank) from the version.php file | ||
:::* Ensure the debug language global in locale in library/globals.inc.php is defaulted to 0 | :::* Ensure the debug language global in locale in library/globals.inc.php is defaulted to 0 | ||
::*Build the zip and tar.gz packages from v_?_?_? and release packages on sourceforge. | ::*Build the zip and tar.gz packages from v_?_?_? and release packages on sourceforge. | ||
==7. Build and release the Ubuntu package.== | |||
::*Ensure new dependencies are added (such as php5-mcrypt) | ::*Ensure new dependencies are added (such as php5-mcrypt) | ||
:8. Build and release the Appliance. | ::*Write and updated dependencies list for installations that can't use the installers | ||
==8. Build and release the Appliance.== | |||
==9. Build and release the Windows XAMPP package.== | |||
Revision as of 06:12, 24 March 2011
1. Create a rel-??? branch from master in the git repo.
2. Release an online development demo that uses the rel-??? branch and updates daily.
3. Publish installation, upgrade, and downloading instructions
- Also provide links for downloading rel-??? packages to allow testing of installation and upgrading by testers
3. Finalize the translations in the rel-??? branch.
4. Bug fix and finalize the rel-??? branch.
5. Create a list of new features in the rel-??? branch (since the last official release)
6. Release rel-??? branch by tagging in git repo with v?_?_?.
- Things to remember before tagging the release.
- Remove dev (make it blank) from the version.php file
- Ensure the debug language global in locale in library/globals.inc.php is defaulted to 0
- Build the zip and tar.gz packages from v_?_?_? and release packages on sourceforge.
7. Build and release the Ubuntu package.
- Ensure new dependencies are added (such as php5-mcrypt)
- Write and updated dependencies list for installations that can't use the installers
