Differences

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

--- dev:release_process:opensrf:2.0 [2012/05/31 00:06] – Update OpenSRF release process to reflect what I did for 2.1.0 dbs
+++ zzz_archive:dev:release_process:opensrf:2.0 [2022/02/10 13:34] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ===== Rolling an OpenSRF release =====
+//Version 2.0 of OpenSRF is deprecated.//
   - Create a local working branch for the release: <code>$ git checkout -b tmp_rel_2_1.0 origin/rel_2_1</code>.  This can be thrown away after you finish the release.
   - Create the Changelog containing the changes for this release only. Since 1.6.0 we have been creating ChangeLogs that show the cumulative changes for a given release in reverse chronological order, distinguishing between alphas, betas, and point releases, with 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 for example: <code bash>
+$ # get the date of the last commit to the previous release
+$ git log osrf_rel_2_0_1 # last commit was 2011-08-19
+$ # this is not perfect, but it's close enough...
 $ git log --pretty --numstat --summary --since 2011-08-19 > ChangeLog.2.1.0
 </code>
@@ Line 11: / Line 16: @@
     * README
   - Follow the steps to build and test the release (see below) and ensure that all tests pass.
   - Push the temporary release branch to origin: <code>git push origin tmp_rel_2_1_0:rel_2_1</code>
   - Create a clean export of the files in a working directory (''/tmp'' in the following example) and generate a tarball that contains the autotools-ized files:<code bash>
 git archive --prefix=opensrf-<version>/ tmp_rel_2_1_0 | (cd /tmp/ && tar xvf -)
 cd /tmp/opensrf-<version>/
-./autogen.sh
+autoreconf -i
 cd ..
 tar zcvf opensrf-2.1.0.tar.gz opensrf-2.1.0/