Release GMT 6.3.0

[maxrjones]

Version: 6.3.0

Scheduled date: November 19, 2021

Before release:

• [x] run src/gmt_make_*.sh to update some .c and .h files
• [x] run admin/gs_check.sh to test if latest ghostscript version works
• [x] check if all tests pass on macOS, Linux and Windows
• [x] check if other GMT-derived projects work well
  • [x] MB-System (@PaulWessel)
  • [x] GMTSAR (@PaulWessel)
  • [x] GMT.jl (@joa-quim)
  • [x] PyGMT (@leouieda, @seisman, @weiji14)
  • [x] gmtmex (@PaulWessel, @joa-quim)
• [x] reserve a DOI on zenodo (@PaulWessel)
• [x] update changelog
• [x] check installation instructions in INSTALL.md
• [x] check if there are any warnings when building the documentation
• [x] add one new entry in doc/rst/_static/version_switch.js if it's a minor release
• [x] check/set values in cmake/ConfigDefault.cmake
  • [x] GMT_VERSION_YEAR is current year
  • [x] GMT_PACKAGE_VERSION_* is correctly set
  • [x] GMT_LIB_SOVERSION is correctly set
  • [x] set GMT_PUBLIC_RELEASE to TRUE
  • [x] update GMT_VERSION_DOI
• [x] freeze codes and commit all changes to GitHub

Release:

• [x] create source tarballs (tar.gz and tar.xz) (@PaulWessel, @meghanrjones)
• [x] create macOS bundle (@PaulWessel, @meghanrjones)
• [x] create Windows installers (win32 and win64) (@joa-quim)
• [x] check if the source tarballs, macOS bundle and Windows installers work well
• [x] upload source tarballs, macOS bundle, Windows installers to the GMT FTP (@PaulWessel, @meghanrjones)
• [x] update README and VERSION files on the GMT FTP (@PaulWessel)
• [x] make a tag and push it to github (Must be done after uploading packages to the GMT FTP)

  # checkout master (for minor releases) or 6.x branch (for patch releases)
  git checkout XXXX
  # create the tag x.x.x
  git tag x.x.x
  # Push tags to GitHub
  git push --tags

• [x] make a GitHub release. The GitHub Actions automatically create a draft release after pushing the tag to github. We need to go to the GitHub Release page, and review it manually.
  • [x] 7 files are attached as release assets (2 source tarballs, 4 installers and 1 checksum file).
  • [x] download the checksum file and check if the checksums are correct
  • [x] edit the draft release, set the target to the correct tag, and publish the release
• [x] upload the tarball to zenodo (@PaulWessel)
• [x] make announcements in the GMT forum
• [x] make announcements on the GMT twitter
• [x] make announcements on the GMT instagram
• [x] update links on the main site (News, Download & Documentation)

After release:

• [x] update GMT_PACKAGE_VERSION_* in cmake/ConfigDefault.cmake
• [x] comment the set (GMT_PUBLIC_RELEASE TRUE) line
• [x] commit changes to GitHub

3rd-party update

Volunteers needed! Please let us know if you volunteer to help to maintain GMT in these 3rd-party tools.

• [x] update conda-forge feedstock (@leouieda, @seisman, @weiji14, @meghanrjones) (https://github.com/conda-forge/gmt-feedstock/pull/178)
• [x] update homebrew formula (@claudiodsf, @seisman) https://github.com/Homebrew/homebrew-core/pull/89808
• [x] update macports ports (@remkos, @seisman) https://github.com/macports/macports-ports/pull/13070
• [x] update the RPM repository (@seisman)
• [x] update the try-gmt Jupyter lab (@weiji14, @seisman) (https://github.com/GenericMappingTools/try-gmt/pull/32)
• [x] update winget manifest file (@seisman) https://github.com/microsoft/winget-pkgs/pull/35396

---

• [x] Party :tada: (don't tick before all other checkboxes are ticked!)

[PaulWessel]

We shall aim to avoid that again.

[Esteban82]

Announcement on instagram done!!

[remkos]

Macports update to 6.3.0 done.

[seisman]

@remkos It seems macports still provides dcw-gmt v1.1.4, but the latest is dcw-gmt v2.0.1.

dcw-gmt v2.0.1 requires GMT>=6.1.1, so updating dcw-gmt from v1.1.4 to v2.0.1 will break the GMT 5 port. Do you have any idea if it's possible to update dcw-gmt to the latest but let the GMT5 port use the old dcw-gmt version?

[Esteban82]

Can this issue be unpinned?