Release GMT 6.1.1

[seisman]

Version: 6.1.1

Scheduled date: Sep 1, 2020

Before release:

• [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] 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] update changelog
• [x] update INSTALL.md
• [x] check if there are any warnings when build the documentation
• [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)
• [x] create macOS bundle (@PaulWessel)
• [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)
• [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)

  git tag x.x.x
  git push --tags

• [x] make a GitHub release. Go to the GitHub Release page, check the draft release (automatically created by github-actions after pushing the tag).
  • [x] 6 files are attached as release assets (2 source tarballs, 3 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] update links on the main site (News, Download & Documentation)

After release:

• [x] create branch 6.x for bug-fixes if this is a minor release (i.e. create branch 6.1 after 6.1.0 is released)

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

• [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

• [x] update conda-forge feedstock (@leouieda, @seisman) (https://github.com/conda-forge/gmt-feedstock/pull/102)
• [x] update homebrew formula (@claudiodsf, @seisman) (https://github.com/Homebrew/homebrew-core/pull/60559)
• [x] update macports ports (@remkos, @seisman) (https://github.com/macports/macports-ports/pull/8298)
• [x] update the RPM repository (@seisman)
• [x] update the try-gmt Jupyter lab (@seisman)
• [x] update the AUR repository (@holishing)

---

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

[seisman]

Will you take care of the draft edit and links, @seisman, and I can start making an announcement message?

Done.

[PaulWessel]

How long until the main gmt site's download page gets updated? I guess triggered by your update so maybe a few minutes? I will wait with posting my forum message until I see it.

[PaulWessel]

Shall I edit the web page stuff? We want to also move teh UNAVCO course to the past tense.

[seisman]

It takes ~1 minutes after pushing changes to the master branch.

[seisman]

The GMT's main site is NOT updated by the CI. We have to update it manually.

[PaulWessel]

OK, unless you have started I can take a crack at that and make a PR?

[seisman]

Go ahead, please.

[PaulWessel]

The next steps about branch do not apply I think. We either stop adding to 6.1 entirely in anticipation of the next release being 6.2 or we hedge and continue what we have done so far. In either case we make no branch. I suppose I should reset the GMT_PUBLIC_RELEASE and update the version ticker anyway, right?

[seisman]

I suppose I should reset the GMT_PUBLIC_RELEASE and update the version ticker anyway, right?

You mean making the changes in the 6.1 branch, right? Do we need to do that? We may delete the 6.1 branch or totally freeze it.

[PaulWessel]

Well, I guess is we agree we aren't doing 6.1 anymore then no point making any edits.

[PaulWessel]

I am OK with that and I think we know @joa-quim is as well.

[joa-quim]

Ofc, but let 6.1.1 alone for a couple of weeks. We never know if something bad wont call fora quick 6.1.2.

I am not against point releases. I'm just against making releases that don't release everything we have at the moment.

[seisman]

Ping @holishing. GMT 6.1.1 is released. Please update AUR when you have time.

[holishing]

AUR updated.

[seisman]

All done. Closing.