a) cd $BUILD_DIR/swig/python/gdal-utils
b) python3 setup.py bdist_wheel
c) Check the output:
twine check dist/gdal_utils-*.whl
c) For trial :
twine upload dist/gdal_utils-*.whl -r pypitest
d) For real :
twine upload dist/gdal_utils-*.whl
18) Generate signed maven artifacts with GPG for Java bindings.
This step is required in order to deploy the
maven artifacts to the central Maven repository. Before this step can
proceed you must set up a signing key as described here:
http://central.sonatype.org/pages/working-with-pgp-signatures.html
a) Each developer can use their own signing key although it is usually best to
avoid constantly using a different key for releases as users will need to
import the public key in order to verify the artifacts.
Here are a quick set of steps to generate a signing key key.
gpg --gen-key
gpg --list-keys (and note the key id)
gpg --keyserver hkp://pool.sks-keyservers.net --send-keys <key id>
See the above link for more details.
b) Run CMake with the following variables:
1. GPG_KEY: the identifier for the signing keys
2. GPG_PASS: the passphrase for the signing key (optional)
c) Build the bindings: make java_binding
Upon success you should see a file named "swig/java/build/maven/bundle.jar"
that contains all the maven artifacts with signatures. This file is what
will be uploaded to maven central. See the next step.
19) Deploy maven artifacts to Maven central.
NOTE: Before you can deploy to maven central you must set up an account
in Sonatype JIRA. That can be done here:
https://issues.sonatype.org/secure/Signup!default.jspa
Once you have an account set up you must be associated with the gdal
project. Create a ticket here asking to be associated with the project:
https://issues.sonatype.org/browse/OSSRH
The entire deployment process is described in detail here:
http://central.sonatype.org/pages/manual-staging-bundle-creation-and-deployment.html
http://central.sonatype.org/pages/releasing-the-deployment.html
The following steps summarize the process.
a) Log into the Sonatype repository manager at https://oss.sonatype.org. Use the
same credentials as your Sonatype JIRA account.
b) Once log in select "Staging Upload" on the left hand side.
c) Select "Artifact Bundle" under "Upload Mode" and then choose the "bundle.jar"
created in the previous Step 22. Finally "Upload Bundle" to start the upload.
d) When the upload has been completed you will be notified that a staging
repository has been created. Note the name of the repository. It should look
something like "orggdal-100x".
e) From the left hand menu navigate to "Staging Repositories". In the search
box look for the staging repository name you noted from the previous section.
Or just search for "gdal". It should be obvious which repository is the
current one.
f) Select the staging repository. If all is well You should see the option to
"Release" (Located as a button near the top of the page). If not it means
there was an issue with the bundle. Consult the "Activity" tab at the bottom
of the page to find out why.
e) Click the "Release" button and that is it! The release should be available in
Maven Central shortly. You can verify this by going to search.maven.org and
searching for "gdal".
18) Create a release on GitHub
Go to https://github.com/OSGeo/gdal/releases/new
And create a release for the vX.Y.Z tag
Attach the following files:
- gdal-X.Y.Z.tar.gz
- gdal-X.Y.Z.tar.gz.sig
- gdal-X.Y.Z.tar.gz.md5
- gdalXYZ.zip
- gdalXYZ.zip.sig
- gdalXYZ.zip.md5
- gdalautotest-X.Y.Z.zip
20) Regenerate Docker images
e.g
./docker/build-all.sh --with-multi-arch --release --tag 3.3.1 --gdal v3.3.1 --proj 8.1.0 --platform linux/arm64,linux/amd64 --push
and update docker/README.md with the latest release
21) Announce release to :
- major release: gdal-devlists.osgeo.org, gdal-announcelists.osgeo.org, news_itemosgeo.org.
- bugfix release: gdal-devlists.osgeo.org, gdal-announcelists.osgeo.org
Example:
- bugfix release: https://lists.osgeo.org/pipermail/gdal-dev/2019-July/050543.html
- feature release: https://lists.osgeo.org/pipermail/gdal-dev/2020-May/052117.html
Note: gdal-announce is moderated. Make sure that your email address is approved
('mod' tick disabled in https://lists.osgeo.org/mailman/admin/gdal-announce/members),
or your message manually approved, with an administrator of the list.
22) For a feature release: after it has been done, in the master branch, update
the VERSION to the next one and in gcore/gdal_version.h.in, update
GDAL_VERSION_MAJOR/_MINOR, GDAL_RELEASE_NAME (with a dev suffix, like "3.7.0dev"),
and set GDAL_RELEASE_DATE to a date like {YEAR}9999.
Update swig/python/gdal-utils/osgeo_utils/__init__.py to something like (3, 6, 99, 0)
if master is 3.7.0dev
23) For bugfixes releases, forward port to master changes done in
doc/source/about_no_title.rst, doc/source/download.rst and doc/source/download_past.rst