root/tags/gdal_1_3_2/HOWTO-RELEASE

Revision 9644, 1.6 kB (checked in by fwarmerdam, 3 years ago)

Removed note about changelog, now gone.

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
Line 
1         Notes on Preparing a GDAL Source Release
2         ========================================
3
4 1) Update the release date, and number information in gcore/gdal_version.h.
5
6 2) Update the VERSION file.
7
8 3) Update LIBGDAL_CURRENT/REVISION/AGE macros in GDALmake.opt.in.
9    - For a release with no interface changes just bump REVISION.
10    - Adding interfaces, bump CURRENT/AGE, set REVISION to 0.
11    - Deleting interfaces / compatibility issues - bump CURRENT, others to zero.
12
13 4) Prepare release overview in the NEWS file.  The cvs2cl.pl script can be
14    useful for collecting a full listing of all CVS log entries.  It can be
15    useful to perform this and some of the other cvs intensive steps on
16    remotesensing.org if possible, to minimize CVS latency.
17
18    eg.
19
20    % cvs2cl.pl > AutoChangeLog
21
22 5) Update the GDAL doc/index_raw.html to refer to the
23    newly to be created version, and commit.
24
25 6) Tag the release set in CVS:
26
27    eg.
28    % cvs tag -F gdal_1_1_6
29
30 6.5) Also tag the "autotest" tree as above.
31
32 7) Create the source distributions using the mkgdaldist.sh script.  The
33    argument should be the version number (ie. 1.1.6).  Hit enter when
34    prompted for a CVS password.
35
36    eg.
37    % mkgdaldist.sh 1.1.6
38
39 7.5) Create a snapshot of the documentation.
40
41  ie. On www.gdal.org:
42  % gdalhtmlupdate.sh
43  % cd
44  % zip -r ~/gdal-web/dl/gdalXXXdoc.zip gdal-web/*.* gdal-web/ogr
45
46 8) Publish the resulting files on www.gdal.org/gdal-web/dl.
47
48 9) Announce release to the gdal-dev@lists.maptools.org, and freegis@freegis.org
49
50 10) Update the freshmeat.net entry for GDAL.
51
52 11) Update the freegis.org entry for GDAL.
Note: See TracBrowser for help on using the browser.