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