Evergreen DokuWiki

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.

1. Create a new branch:

   svn copy svn://svn.open-ils.org/OpenSRF/trunk svn://svn.open-ils.org/OpenSRF/branches/rel_1_4 -m "Create rel_1_4 branch for next major OpenSRF release"

2. Create a clean export of the data:

   svn export svn://svn.open-ils.org/OpenSRF/branches/rel_1_4 /home/dan/OpenSRF-rel_1.4.0

3. Generate ./configure file:

   cd /home/dan/OpenSRF-rel_1.4.0; ./autogen.sh

4. Generate a ChangeLog in reverse chronological order: svn2cl –group-by-day –separate-daylogs -r HEAD:1728 svn:svn.open-ils.org/OpenSRF/branches/rel_1_4 (on Karmic, requires grabbing an updated stylesheet directly from http://arthurdejong.org/svn2cl/downloads.html and dumping into /etc/svn2cl/svn2cl.xsl) - Tar it up: <code>cd /home/dan; tar czf OpenSRF-rel_1.4.0-beta.tar.gz OpenSRF-rel_1.4.0-beta</code> - Create an md5 hash for the package: <code>md5sum OpenSRF-rel_1_4_0-beta.tar.gz > OpenSRF-rel_1.4.0-beta.tar.gz.md5</code>