Release GMT 6.2.0

[maxrjones]

Version: 6.2.0

Scheduled date: June 05, 2021

Before release:

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

Release:

• create source tarballs (tar.gz and tar.xz) (@PaulWessel, @meghanrjones)
• create macOS bundles (arm64 and intel) (@PaulWessel, @meghanrjones)
• create Windows installers (win32 and win64) (@joa-quim)
• check if the source tarballs, macOS bundle and Windows installers work well
• upload source tarballs, macOS bundle, Windows installers to the GMT FTP (@PaulWessel, @meghanrjones)
• update README and VERSION files on the GMT FTP (@PaulWessel)
• 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

• 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.
  • 7 files are attached as release assets (2 source tarballs, 4 installers and 1 checksum file).
  • download the checksum file and check if the checksums are correct
  • edit the draft release, set the target to the correct tag, and publish the release
• upload the tarball to zenodo (@PaulWessel)
• make announcements in the GMT forum
• make announcements on the GMT twitter
• update links on the main site (News, Download & Documentation)

After release:

• create branch 6.x for bug-fixes if this is a minor release (i.e. create branch 6.2 after 6.2.0 is released)

  git checkout master
  git checkout -b 6.2
  git push --set-upstream origin 6.2
  

• update GMT_PACKAGE_VERSION_* in cmake/ConfigDefault.cmake
• comment the set (GMT_PUBLIC_RELEASE TRUE) line
• 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.

• update conda-forge feedstock (@leouieda, @seisman, @weiji14) (Bump to GMT 6.2.0 conda-forge/gmt-feedstock#153)
• update homebrew formula (@claudiodsf, @seisman) (gmt 6.2.0 Homebrew/homebrew-core#78822)
• update macports ports (@remkos, @seisman) (gmt6: update to 6.2.0 macports/macports-ports#11253)
• update the RPM repository (@seisman) (Done in Bump to GMT 6.2.0 gmt-rpm#6, except CentOS 8, see GMT 6.2.0 fails to build on CentOS 8 due to upstream issues gmt-rpm#7)
• update the try-gmt Jupyter lab (@seisman) (Bump to GMT 6.2.0 try-gmt#20)
• update the AUR repository (@holishing)
• update winget manifest file (@seisman) (GenericMappingTools.gmt version 6.2.0 microsoft/winget-pkgs#16400)

---

• Party 🎉 (don't tick before all other checkboxes are ticked!)

[PaulWessel]

Need @joa-quim to do his GMT.jl tests.

[holishing]

Detail: Version number in 1st task of “After Release” should be corrected. :)

[PaulWessel]

ARM64 bundle completed and uploaded to gmtrelease dir:

b5bcb8bffb4db8a42fcc08012a04399ccc6070f3a4b8ee36975f8c0e74b0bc4f gmt-6.2.0-darwin-arm64.dmg

[maxrjones]

c5038aff92be4ac9df1fc2f06c1b23f5eec9e111bfe596c7ae2b47305ac929a9  gmt-6.2.0-darwin-x86_64.dmg
ab7062912aeead1021770fad4756e0a99860fde8ea9b428fb00c22fa15a3bbfc  gmt-6.2.0-src.tar.gz
a01f0a14d48bbc0b14855670f366df3cb8238f0ccdfa26fe744968b4f1c14d54  gmt-6.2.0-src.tar.xz

[PaulWessel]

Hi @joa-quim, please build the Windows installer and make it available, with checksum.

[joa-quim]

http://fct-gmt.ualg.pt/tmp/gmt-6.2.0-win32.exe
SHA1 hash of .\gmt-6.2.0-win32.exe: bc44e8ecfe2b5c1962d7f1a17f5d1e39aedd71b2

http://fct-gmt.ualg.pt/tmp/gmt-6.2.0-win64.exe
SHA1 hash of .\gmt-6.2.0-win64.exe: 5bac8d815c8a4d78c7cb2c59e984d68d32c8b3ae

[PaulWessel]

Thanks, we should now do some testing that these are all functioning. I have placed them in the gmtrelease folder and verified the sha1 values.

[PaulWessel]

To the CI people: Might it be possible to device a simple cloud-run test of the installers? I.e., have the CI download an installer, install GMT, and run a some basic steps? RIght now testing the installers requires one to have access to a machine or VM that supports the various OS. Having lent my Win laptop to a student I have no Win here at home, just mac intel and arm, and maybe CentOS in a VM on the mac.

[seisman]

We already have a test bot (https://github.com/GenericMappingTools/gmt-release-testbot) which can test the installer on various OS. I'll trigger testing on the installers now.

[PaulWessel]

Great, perhaps the checklist can remind us of what that entails for next time?

[seisman]

Could you please remind me what's the URL link of the "gmtrelease folder"?

[seisman]

Could you please remind me what's the URL link of the "gmtrelease folder"?

I just found it.