Ignore:
Timestamp:
May 5, 2011, 5:36:53 AM (14 years ago)
Author:
Dmitry A. Kuminov
Message:

trunk: Merged in qt 4.7.2 sources from branches/vendor/nokia/qt.

Location:
trunk
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • trunk

  • trunk/src/3rdparty/libtiff/HOWTO-RELEASE

    r2 r846  
    11HOWTO-RELEASE:
    22
    3 Notes on releasing. You will need appropriate autoconf, automake and libtool
    4 utilities to release a package.
     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.6 or later is needed in order to avoid bugs in m4. These
     11   packages may be downloaded from the following ftp locations:
     12
     13     autoconf - ftp://ftp.gnu.org/pub/gnu/autoconf
     14     automake - ftp://ftp.gnu.org/pub/gnu/automake
     15     libtool  - ftp://ftp.gnu.org/pub/gnu/libtool
     16
     17   Release builds should only be done on a system with a functioning
     18   and correctly set system clock and on a filesystem which accurately
     19   records file update times.  Use of GNU make is recommended.
    520
    6211. Commit any unsaved changes.
    722
    8 2. "make clean"
    9 
    10 3. Create html/vX.X.html.  Take ChangeLog entries and html-ify in there.
     232. Create html/vX.X.html.  Take ChangeLog entries and html-ify in there.
    1124   Easist thing to do is take html/vX.(X-1).html and use it as a template.
    1225   Add that file to the list of EXTRA_DIST files in the html/Makefile.am.
    1326
    14 3.5. Update html/index.html to refer to this new page as the current release.
     273. Update html/index.html to refer to this new page as the current release.
    1528
    16 4. Increment version in configure.ac.  Put 'alpha' or 'beta' after
    17    the version, if applicable.
     294. Increment the release version in configure.ac.  Put 'alpha' or
     30   'beta' after the version, if applicable.  For example:
    1831
    19    eg.
    20    3.5.7
    21     or
    22    3.5.8beta
     32     3.9.1
     33      or
     34     3.9.1beta
    2335
    2436   Version should be updated in two places: in the second argument of the
    2537   AC_INIT macro and in LIBTIFF_xxx_VERSION variables.
    2638
    27 5. autoconf
     395. Add an entry to Changelog similar to:
    2840
    29 6. sh configure
     41     * libtiff 3.9.1 released.
    3042
    31 7. make release -- this will update "RELEASE-DATE" and "VERSION" in the top
    32    level dir, and libtiff/tiffvers.h. 
     436. In the source tree do
    3344
    34 8. Please verify that the version info in RELEASE-DATE, VERSION and
    35    libtiff/tiffvers.h is right.
     45     ./autogen.sh
    3646
    37 9. make; make distcheck (to test).
     47   This step may be skipped if you have already been using a
     48   maintainer build with current autoconf, automake, and libtool
     49   packages.  It is only needed when updating tool versions.
    3850
    39 10. make distclean
     517. It is recommended (but not required) to build outside of the source
     52   tree so that the source tree is kept in a pristine state.  This
     53   also allows sharing the source directory on several networked
     54   systems.  For example:
    4055
    41 11. cvs commit
     56     mkdir libtiff-build
     57     cd libtiff-build
     58     /path/to/libtiff/configure --enable-maintainer-mode
    4259
    43 12. cvs tag Release-v3-5-7 (or the appropriate name for the release)
     60   otherwise do
    4461
    45 13. configure; make dist
     62     ./configure --enable-maintainer-mode
     63
     648. In the build tree do
     65
     66     make release
     67
     68   This will update "RELEASE-DATE", "VERSION", and libtiff/tiffvers.h
     69   in the source tree.
     70
     719. In the source tree, verify that the version info in RELEASE-DATE,
     72   VERSION and libtiff/tiffvers.h is right.
     73
     7410. In the build tree do
     75
     76      make
     77      make distcheck
     78
     79    If 'make distcheck' fails, then correct any issues until it
     80    succeeds.
     81
    4682    Two files with names tiff-version.tar.gz and tiff-version.zip will
    47     be created in the top level package directory.
     83    be created in the top level build directory.
    4884
    49 14. Copy to ftp.remotesensing.org ftp site.
    50     scp tiff-*.tar.gz ftp.remotesensing.org:/var/ftp/libtiff/
    51     scp tiff-*.zip ftp.remotesensing.org:/var/ftp/libtiff/
     8511. In the source tree do
    5286
    53 15. Announce to list, tiff@lists.maptools.org
     87      'cvs commit'.
    5488
    55 16. Update libtiff page on freshmeat with new version announcement.
     8912. In the source tree do
     90
     91      cvs tag Release-v3-9-1
     92
     93    (or the appropriate name for the release)
     94
     9513. Copy release packages from the build tree to the
     96    ftp.remotesensing.org ftp site.
     97
     98      scp tiff-*.tar.gz tiff-*.zip \
     99         frankw@upload.osgeo.org:/osgeo/download/libtiff
     100
     10114. Announce to list, tiff@lists.maptools.org
     102
     10315. Update libtiff page on freshmeat with new version announcement.
    56104
    57105
Note: See TracChangeset for help on using the changeset viewer.