User Tools

Site Tools


dev:rolling_a_release

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
dev:rolling_a_release [2011/03/10 21:11] – Update with a recent version for OpenSRF dbsdev:rolling_a_release [2011/03/18 10:39] – testing FTW gmcharlton
Line 7: Line 7:
 svn copy svn://svn.open-ils.org/OpenSRF/branches/rel_2_0 svn://svn.open-ils.org/OpenSRF/tags/rel_2_0_0_rc2 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"</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/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-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_2_0</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_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)
 +  - 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-2.0.0-rc2; ./autogen.sh</code>
   - Tar it up: <code>cd /home/dan; tar czf opensrf-2.0.0-rc2.tar.gz opensrf-2.0.0-rc2</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-2.0.0-rc2.tar.gz > opensrf-2.0.0-rc2.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>
 +  - //Bonus hygiene step:// Take the tarball you just created and test installing OpenSRF from it; at the very least, ensure that ''make check'' passes.
  

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

© 2008-2022 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a U.S. 501(c)3 non-profit organization.