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