summaryrefslogtreecommitdiff
path: root/tiff/HOWTO-RELEASE
diff options
context:
space:
mode:
Diffstat (limited to 'tiff/HOWTO-RELEASE')
-rw-r--r--tiff/HOWTO-RELEASE105
1 files changed, 105 insertions, 0 deletions
diff --git a/tiff/HOWTO-RELEASE b/tiff/HOWTO-RELEASE
new file mode 100644
index 0000000..4bf4de7
--- /dev/null
+++ b/tiff/HOWTO-RELEASE
@@ -0,0 +1,105 @@
+HOWTO-RELEASE:
+
+Notes on releasing.
+
+0. Make sure that you have current FSF releases of autoconf, automake,
+ and libtool packages installed under a common installation prefix
+ and that these tools are in your executable search path prior to
+ any other installed versions. Versions delivered with Linux may be
+ altered so it is best to install official FSF releases. GNU 'm4'
+ 1.4.6 or later is needed in order to avoid bugs in m4. These
+ packages may be downloaded from the following ftp locations:
+
+ autoconf - ftp://ftp.gnu.org/pub/gnu/autoconf
+ automake - ftp://ftp.gnu.org/pub/gnu/automake
+ libtool - ftp://ftp.gnu.org/pub/gnu/libtool
+
+ Release builds should only be done on a system with a functioning
+ and correctly set system clock and on a filesystem which accurately
+ records file update times. Use of GNU make is recommended.
+
+1. Commit any unsaved changes.
+
+2. Create html/vX.X.html. Take ChangeLog entries and html-ify in there.
+ Easist thing to do is take html/vX.(X-1).html and use it as a template.
+ Add that file to the list of EXTRA_DIST files in the html/Makefile.am.
+
+3. Update html/index.html to refer to this new page as the current release.
+
+4. Increment the release version in configure.ac. Put 'alpha' or
+ 'beta' after the version, if applicable. For example:
+
+ 3.9.1
+ or
+ 3.9.1beta
+
+ Version should be updated in two places: in the second argument of the
+ AC_INIT macro and in LIBTIFF_xxx_VERSION variables.
+
+5. Add an entry to Changelog similar to:
+
+ * libtiff 3.9.1 released.
+
+6. In the source tree do
+
+ ./autogen.sh
+
+ This step may be skipped if you have already been using a
+ maintainer build with current autoconf, automake, and libtool
+ packages. It is only needed when updating tool versions.
+
+7. It is recommended (but not required) to build outside of the source
+ tree so that the source tree is kept in a pristine state. This
+ also allows sharing the source directory on several networked
+ systems. For example:
+
+ mkdir libtiff-build
+ cd libtiff-build
+ /path/to/libtiff/configure --enable-maintainer-mode
+
+ otherwise do
+
+ ./configure --enable-maintainer-mode
+
+8. In the build tree do
+
+ make release
+
+ This will update "RELEASE-DATE", "VERSION", and libtiff/tiffvers.h
+ in the source tree.
+
+9. In the source tree, verify that the version info in RELEASE-DATE,
+ VERSION and libtiff/tiffvers.h is right.
+
+10. In the build tree do
+
+ make
+ make distcheck
+
+ If 'make distcheck' fails, then correct any issues until it
+ succeeds.
+
+ Two files with names tiff-version.tar.gz and tiff-version.zip will
+ be created in the top level build directory.
+
+11. In the source tree do
+
+ 'cvs commit'.
+
+12. In the source tree do
+
+ cvs tag Release-v3-9-2
+
+ (or the appropriate name for the release)
+
+13. Copy release packages from the build tree to the
+ ftp.remotesensing.org ftp site.
+
+ scp tiff-*.tar.gz tiff-*.zip \
+ frankw@upload.osgeo.org:/osgeo/download/libtiff
+
+14. Announce to list, tiff@lists.maptools.org
+
+15. Update libtiff page on freshmeat with new version announcement.
+
+