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