1HOWTO-RELEASE: 2 3Notes on releasing. 4 50. Make sure that you have current FSF releases of autoconf, automake, 6 and libtool packages installed under a common installation prefix 7 and that these tools are in your executable search path prior to 8 any other installed versions. Versions delivered with Linux may be 9 altered so it is best to install official FSF releases. GNU 'm4' 10 1.4.16 is needed in order to avoid bugs in m4. These packages may 11 be downloaded from the following ftp locations: 12 13 m4 - ftp://ftp.gnu.org/pub/gnu/m4 14 autoconf - ftp://ftp.gnu.org/pub/gnu/autoconf 15 automake - ftp://ftp.gnu.org/pub/gnu/automake 16 libtool - ftp://ftp.gnu.org/pub/gnu/libtool 17 18 It is recommanded building m4 before autoconf, since the latest requires 19 the former. 20 21 Release builds should only be done on a system with a functioning 22 and correctly set system clock and on a filesystem which accurately 23 records file update times. Use of GNU make is recommended. 24 251. Commit any unsaved changes. 26 272. Create html/vX.X.html. Take ChangeLog entries and html-ify in there. 28 Easist thing to do is take html/vX.(X-1).html and use it as a template. 29 Add that file to the list of EXTRA_DIST files in the html/Makefile.am. 30 313. Update html/index.html to refer to this new page as the current release. 32 334. Increment the release version in configure.ac. Put 'alpha' or 34 'beta' after the version, if applicable. For example: 35 36 4.0.0 37 or 38 4.0.0beta7 39 40 Version should be updated in two places: in the second argument of the 41 AC_INIT macro and in LIBTIFF_xxx_VERSION variables. 42 435. Update library ELF versioning in configure.ac (LIBTIFF_CURRENT, 44 LIBTIFF_REVISION, and LIBTIFF_AGE). These numbers have nothing to 45 do with the libtiff release version numbers. 46 47 Note that as of libtiff 4.X, proper ELF versioning is used so 48 please follow the rules listed in configure.ac. At a bare minimum, 49 you should increment LIBTIFF_REVISION for each release so that 50 installed library files don't overwrite existing files. If APIs 51 have been added, removed, or interface structures have changed, 52 then more care is required. 53 546. Add an entry to Changelog similar to: 55 56 * libtiff 4.0.0 released. 57 587. In the source tree do 59 60 ./autogen.sh 61 62 This step may be skipped if you have already been using a 63 maintainer build with current autoconf, automake, and libtool 64 packages. It is only needed when updating tool versions. 65 668. It is recommended (but not required) to build outside of the source 67 tree so that the source tree is kept in a pristine state. This 68 also allows sharing the source directory on several networked 69 systems. For example: 70 71 mkdir libtiff-build 72 cd libtiff-build 73 /path/to/libtiff/configure --enable-maintainer-mode 74 75 otherwise do 76 77 ./configure --enable-maintainer-mode 78 799. In the build tree do 80 81 make release 82 83 This will update "RELEASE-DATE", "VERSION", and libtiff/tiffvers.h 84 in the source tree. 85 8610. In the source tree, verify that the version info in RELEASE-DATE, 87 VERSION and libtiff/tiffvers.h is right. 88 8911. In the build tree do 90 91 make 92 make distcheck 93 94 If 'make distcheck' fails, then correct any issues until it 95 succeeds. 96 97 Two files with names tiff-version.tar.gz and tiff-version.zip will 98 be created in the top level build directory. 99 10012. In the source tree do 101 102 'cvs commit'. 103 10413. In the source tree do 105 106 cvs tag Release-v4-0-0 107 108 (or the appropriate name for the release) 109 11014. Copy release packages from the build tree to the 111 ftp.remotesensing.org ftp site. 112 113 scp tiff-*.tar.gz tiff-*.zip \ 114 [email protected]:/osgeo/download/libtiff 115 11615. Announce to list, [email protected] 117 118