Increment version to 4.9.2 in preparation for release

1 files changed, 23 insertions, 18 deletions

diff --git a/HOWTO-RELEASE b/HOWTO-RELEASE
index cd4645f6..bc763f4f 100644
--- a/HOWTO-RELEASE
+++ b/HOWTO-RELEASE
@@ -3,25 +3,30 @@
 
 1) Update the version number in configure.in (in AC_INIT()).
 
+   1a) Update the version number in PROJ_BUILD_VERSION in CMakeLists.txt
+
 2) Update the version number in proj_api.h (#define PJ_VERSION).
 
 3) Update the version number, and date in src/pj_release.c.
 
-4) Update the version number in the -version-info definition in 
-   src/Makefile.am.  It consists of "current:revision:age".  Set 
+4) Update the version number in the -version-info definition in
+   src/Makefile.am.  It consists of "current:revision:age".  Set
    the same in the PROJ_SOVERSION variable in CMakeLists.txt
 
-   - If the library source code has changed at all since the last update, 
-     then increment revision (c:r:a becomes c:r+1:a). 
+   4a) Increment PROJ_BUILD_VERSION in CMakeLists.txt to follow
+       libtool versioning
+
+   - If the library source code has changed at all since the last update,
+     then increment revision (c:r:a becomes c:r+1:a).
 
-   - If any interfaces have been added, removed, or changed since the last 
-     update, increment current, and set revision to 0. 
+   - If any interfaces have been added, removed, or changed since the last
+     update, increment current, and set revision to 0.
 
-   - If any interfaces have been added since the last public release, then 
-     increment age. 
+   - If any interfaces have been added since the last public release, then
+     increment age.
 
-   - If any interfaces have been removed since the last public release, then 
-     set age to 0. 
+   - If any interfaces have been removed since the last public release, then
+     set age to 0.
 
 4.5) Run "autogen.sh" (hopefully on the same machine it was last run on)
 
@@ -36,33 +41,33 @@
     - %setup line
     - rm -rf line
 
-8) If this is a major release, prepare a branch. 
+8) If this is a major release, prepare a branch.
 
    svn copy https://svn.osgeo.org/metacrs/proj/trunk \
             https://svn.osgeo.org/metacrs/proj/branches/4.7
 
-9) Tag the release set in SVN 
+9) Tag the release set in SVN
 
    svn copy https://svn.osgeo.org/metacrs/proj/branches/4.7 \
             https://svn.osgeo.org/metacrs/proj/tags/4.7.0
 
 10) Do a "make dist-all" in the proj root directory.  After some grinding
    this should result in files like proj-4.4.3.tar.gz and proj-4.4.3.zip
-   being created.  These are full source distributions. 
+   being created.  These are full source distributions.
 
-11) Put these in the proj ftp area on /osgeo/download/proj on 
-   download.osgeo.org.  This can be done via scp using a command like the 
+11) Put these in the proj ftp area on /osgeo/download/proj on
+   download.osgeo.org.  This can be done via scp using a command like the
    following.
 
   scp proj-4.4.3.{tar.gz,zip} warmerdam@download.osgeo.org:/osgeo/download/proj
 
-12) Announce the new release on the PROJ.4 and MetaCRS mailing lists. 
+12) Announce the new release on the PROJ.4 and MetaCRS mailing lists.
 
-13) Issue a new release report on Freshmeat.  
+13) Issue a new release report on Freshmeat.
 
    http://freshmeat.net/projects/proj.4/
 
 NOTES:
 
  o Information about preparing binary releases, and RPMs should be formalized.
- o A "beta" release step should likely be incorporated. 
+ o A "beta" release step should likely be incorporated.