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 tagged release from the rel_2_0 branch.
- Create a new branch:
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 "Tag for 2.0.0 RC2 release"
- Create a clean export of the data:
svn export svn://svn.open-ils.org/OpenSRF/tags/rel_2_0_0_rc2 /home/dan/opensrf-2.0.0-rc2
. As of 1.6.0, we have started using lower case directory and package names to comply with Debian packaging standards.
- Generate ./configure file:
cd /home/dan/opensrf-2.0.0-rc2; ./autogen.sh
- Generate a ChangeLog in reverse chronological order:
svn2cl --group-by-day --separate-daylogs --linelen 90 -r HEAD:2020 svn://svn.open-ils.org/OpenSRF/branches/rel_2_0
- 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 version stamp in the tagged release (edit src/perl/lib/OpenSRF.pm)
- Tar it up:
cd /home/dan; tar czf opensrf-2.0.0-rc2.tar.gz opensrf-2.0.0-rc2
- Create an md5 hash for the package:
md5sum opensrf-2.0.0-rc2.tar.gz > opensrf-2.0.0-rc2.tar.gz.md5
dev/rolling_a_release.1299809507.txt.gz · Last modified: 2022/02/10 13:34 (external edit)