| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| dev:rolling_a_release [2010/09/17 12:17] – Note ChangeLog structure change and lowercase naming for Debian dbs | dev:rolling_a_release [2011/03/10 21:11] – Update with a recent version for OpenSRF dbs |
|---|
| ==== Rolling an OpenSRF release ==== | ==== Rolling an OpenSRF release ==== |
| |
| Rough notes, assuming you're using ''/home/dan'' as your working directory and cutting a new branch from trunk to rel_1_4. In most real world cases, it would be rel_1_4 to rel_1_4_#. Also, you would normally tag the release. | Rough notes, assuming you're using ''/home/dan'' as your working directory and cutting a new tagged release from the rel_2_0 branch. |
| |
| - Create a new branch:<code> | - Create a new branch:<code> |
| svn copy svn://svn.open-ils.org/OpenSRF/trunk svn://svn.open-ils.org/OpenSRF/branches/rel_1_6 | svn copy svn://svn.open-ils.org/OpenSRF/branches/rel_2_0 svn://svn.open-ils.org/OpenSRF/tags/rel_2_0_0_rc2 |
| -m "Create rel_1_4 branch for next major OpenSRF release"</code> | -m "Tag for 2.0.0 RC2 release"</code> |
| - Create a clean export of the data: <code>svn export svn://svn.open-ils.org/OpenSRF/branches/rel_1_6 /home/dan/opensrf-1.6.0</code>. As of 1.6.0, we have started using lower case directory and package names to comply with Debian packaging standards. | - Create a clean export of the data: <code>svn export svn://svn.open-ils.org/OpenSRF/tags/rel_2_0_0_rc2 /home/dan/opensrf-2.0.0-rc2</code>. As of 1.6.0, we have started using lower case directory and package names to comply with Debian packaging standards. |
| - Generate ./configure file: <code>cd /home/dan/opensrf-1.6.0; ./autogen.sh</code> | - Generate ./configure file: <code>cd /home/dan/opensrf-2.0.0-rc2; ./autogen.sh</code> |
| - Generate a ChangeLog in reverse chronological order: <code>svn2cl --group-by-day --separate-daylogs --linelen 90 -r HEAD:2020 svn://svn.open-ils.org/OpenSRF/branches/rel_1_6</code> (on Karmic, requires grabbing an updated stylesheet directly from http://arthurdejong.org/svn2cl/downloads.html and dumping into /etc/svn2cl/svn2cl.xsl). | - Generate a ChangeLog in reverse chronological order: <code>svn2cl --group-by-day --separate-daylogs --linelen 90 -r HEAD:2020 svn://svn.open-ils.org/OpenSRF/branches/rel_2_0</code> |
| * Note: I have started creating ChangeLogs that show the cumulative changes for a given release, distinguishing between alphas, betas, and point releases. Basically ''cat ChangeLog.old >> ChangeLog.new'' and add a header distinguishing each block of changes. That way we will not have to link to ten different ChangeLogs if we reach 1.6.10. | * Note: I have started creating ChangeLogs that show the cumulative changes for a given release, distinguishing between alphas, betas, and point releases. Basically ''cat ChangeLog.old >> ChangeLog.new'' and add a header distinguishing each block of changes. That way we will not have to link to ten different ChangeLogs if we reach 1.6.10. |
| - Update the ChangeLog in the tagged release (check it in to the tag) | - Update the ChangeLog in the tagged release (check it in to the tag) |
| - Update the version stamp in the tagged release (edit src/perl/lib/OpenSRF.pm) | - Update the version stamp in the tagged release (edit src/perl/lib/OpenSRF.pm) |
| - Tar it up: <code>cd /home/dan; tar czf opensrf-1.6.0.tar.gz opensrf-1.6.0</code> | - Tar it up: <code>cd /home/dan; tar czf opensrf-2.0.0-rc2.tar.gz opensrf-2.0.0-rc2</code> |
| - Create an md5 hash for the package: <code>md5sum opensrf-1_6_0.tar.gz > opensrf-1.4.0.tar.gz.md5</code> | - Create an md5 hash for the package: <code>md5sum opensrf-2.0.0-rc2.tar.gz > opensrf-2.0.0-rc2.tar.gz.md5</code> |
| |
