Difference between revisions of "Steps for an official release"
From OpenEMR Project Wiki
Bradymiller (talk | contribs) |
Bradymiller (talk | contribs) |
||
| Line 16: | Line 16: | ||
git clone git://openemr.git.sourceforge.net/gitroot/openemr/openemr | git clone git://openemr.git.sourceforge.net/gitroot/openemr/openemr | ||
git checkout origin/v4_0_0 | git checkout origin/v4_0_0 | ||
rm -fr openemr/.git | rm -fr openemr/.git | ||
chmod -R u+w openemr | chmod -R u+w openemr | ||
chmod -R a+w openemr/sites/default/documents openemr/sites/default/edi openemr/sites/default/era | chmod -R a+w openemr/sites/default/documents openemr/sites/default/edi openemr/sites/default/era | ||
chmod a+w openemr/sites/default/sqlconf.php | chmod a+w openemr/sites/default/sqlconf.php | ||
chmod a+w openemr/gacl/admin/templates_c | chmod a+w openemr/gacl/admin/templates_c | ||
chmod a+w openemr/sites/default/config.php | chmod a+w openemr/sites/default/config.php | ||
chmod -R a+w openemr/interface/main/calendar/modules/PostCalendar/pntemplates/cache | chmod -R a+w openemr/interface/main/calendar/modules/PostCalendar/pntemplates/cache | ||
chmod -R a+w openemr/interface/main/calendar/modules/PostCalendar/pntemplates/compiled | chmod -R a+w openemr/interface/main/calendar/modules/PostCalendar/pntemplates/compiled | ||
mv openemr openemr-4.0.0 | mv openemr openemr-4.0.0 | ||
===Linux (tarball)=== | ===Linux (tarball)=== | ||
tar zcpf openemr-4.0.0.tar.gz openemr-4.0.0 | tar zcpf openemr-4.0.0.tar.gz openemr-4.0.0 | ||
===Windows (zip)=== | ===Windows (zip)=== | ||
zip -r openemr-4.0.0.zip openemr-4.0.0 | zip -r openemr-4.0.0.zip openemr-4.0.0 | ||
===Sourceforge Upload=== | ===Sourceforge Upload=== | ||
Revision as of 06:27, 24 March 2011
Overview
Steps detailing a release of 4.0.
1. Create a rel-400 branch from master in the git repo.
2. Release an online development demo that uses the rel-400 branch and updates daily.
3. Publish installation, upgrade, and downloading instructions
- Also provide links for downloading rel-400 packages to allow testing of installation and upgrading by testers
3. Finalize the translations in the rel-400 branch.
4. Bug fix and finalize the rel-400 branch.
5. Create a list of new features in the rel-400 branch (since the last official release)
6. Release rel-400 branch by tagging in git repo with v4_0_0.
- 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
7.Build the zip and tar.gz packages from v4_0_0 and release packages on sourceforge.
git clone git://openemr.git.sourceforge.net/gitroot/openemr/openemr git checkout origin/v4_0_0 rm -fr openemr/.git chmod -R u+w openemr chmod -R a+w openemr/sites/default/documents openemr/sites/default/edi openemr/sites/default/era chmod a+w openemr/sites/default/sqlconf.php chmod a+w openemr/gacl/admin/templates_c chmod a+w openemr/sites/default/config.php chmod -R a+w openemr/interface/main/calendar/modules/PostCalendar/pntemplates/cache chmod -R a+w openemr/interface/main/calendar/modules/PostCalendar/pntemplates/compiled mv openemr openemr-4.0.0
Linux (tarball)
tar zcpf openemr-4.0.0.tar.gz openemr-4.0.0
Windows (zip)
zip -r openemr-4.0.0.zip openemr-4.0.0
Sourceforge Upload
Upload via Project Admin Upload release and a release notes file Set file properties appropriately
8. 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
