dev:rolling_a_release
This is an old revision of the document!
Rolling Evergreen and OpenSRF releases
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.
- 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"
- Create a clean export of the data:
svn export svn://svn.open-ils.org/OpenSRF/branches/rel_1_4 /home/dan/OpenSRF-1.4.0
- Generate ./configure file:
cd /home/dan/OpenSRF-1.4.0; ./autogen.sh
- Generate a ChangeLog in reverse chronological order:
svn2cl --group-by-day --separate-daylogs --linelen 90 -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)
- 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)
- Tar it up:
cd /home/dan; tar czf OpenSRF-1.4.0-beta.tar.gz OpenSRF-1.4.0-beta
- Create an md5 hash for the package:
md5sum OpenSRF-1_4_0-beta.tar.gz > OpenSRF-1.4.0-beta.tar.gz.md5
dev/rolling_a_release.1277951346.txt.gz · Last modified: 2022/02/10 13:34 (external edit)