Release GMT 6.5.0

[PaulWessel]

Version: 6.5

Scheduled date: Jan, 5, 2024

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, @maxrjones)
  • [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 the version information in CITATION.cff
• [x] check installation instructions in install.rst
• [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)
• [x] create macOS bundle (@PaulWessel)
• [x] create Windows win64 installer (@joa-quim)
• [x] create Windows win64 portable (@joa-quim?)
• [x] check if the source tarballs for Linux work well (@Esteban82, @anbj)
• [x] check if the macOS bundles work well (@seisman, @maxrjones)
• [x] check if the Windows installers work well (volunteers needed!)
• [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)

  # checkout master (for minor releases) or 6.x branch (for patch releases)
  git checkout XXXX
  # create the tag 6.5
  git tag6.5
  # 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
• [ ] make announcements on the GMT twitter
• [x] make announcements on the GMT Instagram
• [x] update links on the main site (Download & Documentation) https://github.com/GenericMappingTools/website/pull/150
• [ ] update install instructions on the wiki if needed

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.5
  git push --set-upstream origin 6.5

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

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) https://github.com/conda-forge/gmt-feedstock/pull/282
• [x] update homebrew formula (@claudiodsf, @seisman) https://github.com/Homebrew/homebrew-core/commit/e95a7cae0fa53cc2662784afec79b2bce1ae36fc
• [x] update macports ports (@remkos, @seisman) https://github.com/macports/macports-ports/pull/22084
• [x] update the RPM repository (@seisman)
• [x] update the try-gmt Jupyter lab (@weiji14, @seisman, @maxrjones)
• [x] update winget manifest file (@seisman) https://github.com/microsoft/winget-pkgs/pull/133249

---

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

[maxrjones]

A couple options:

1. Remko and I could setup a zoom or async work on debugging the dvc issues
2. We could remove https://github.com/GenericMappingTools/gmt/blob/af1a38b864b53dcd12aca296b97ed3608b9ef63d/admin/ConfigReleaseBuild.cmake#L27-L34 since I do not think Paul or I have the ability to codesign the bundle anymore. This would allow @PaulWessel to build from the Hawaii Mac Pro.

[PaulWessel]

Yes, that works. Instead of removing (because the signing worked on my M1) I will add another option, e.g., -s, that is needed to do signing. Thanks @maxrjones for reminding me where that happened.

[PaulWessel]

Remind me, your UH account is maxjones or mjones?

[PaulWessel]

admin/bulid-release [-s] now works. I signed it on arm64 and not on X68_64.

[PaulWessel]

@seisman, I think we are good to release 6.5. no? I would feel better if you handled the release stuff (git, GitHub, and set tag etc) as I tend to foul that up.. Once released I can do the release of new oceania data (or @Esteban82 could if he is able to).

[seisman]

OK. I'll let you know when I finish the git release.

[seisman]

@PaulWessel Could you please upload the tarballs and installers to the GMT FTP first?

[PaulWessel]

SUre, forgot. I put them on my pub release page but will do this now.

[PaulWessel]

Done, I hope, even with correct permission I think.

[seisman]

The file permissions are incorrect.

[seisman]

Win installer and portable

https://fct-gmt.ualg.pt/tmp/GMT5/gmt-6.5.0-win64.exe 0B4D47058E0B00F20A467DBA260AAB6238B705E8C6C6FA5B0D7FB237410532E2

https://fct-gmt.ualg.pt/tmp/GMT5/gmt-6.5.0-win64.zip DE7E05F87896FFB87E73F24EFB2FE21BE608CDED02AE0C3569652866E1448658

Quick question: we no longer provide the win32 installer?

[PaulWessel]

No, those are deprecated I think, per @joa-quim .

[seisman]

Win installer and portable https://fct-gmt.ualg.pt/tmp/GMT5/gmt-6.5.0-win64.exe 0B4D47058E0B00F20A467DBA260AAB6238B705E8C6C6FA5B0D7FB237410532E2 https://fct-gmt.ualg.pt/tmp/GMT5/gmt-6.5.0-win64.zip DE7E05F87896FFB87E73F24EFB2FE21BE608CDED02AE0C3569652866E1448658

Quick question: we no longer provide the win32 installer?

OK, we dropped the win32 support in https://github.com/GenericMappingTools/gmt/issues/6857.

[seisman]

@PaulWessel The file permissions on the FTP are still incorrect.

[PaulWessel]

You mean the binary files. Yes. just added r t to group and other.

[seisman]

The win64 installer is likely incorrect.

Win installer and portable

https://fct-gmt.ualg.pt/tmp/GMT5/gmt-6.5.0-win64.exe 0B4D47058E0B00F20A467DBA260AAB6238B705E8C6C6FA5B0D7FB237410532E2

https://fct-gmt.ualg.pt/tmp/GMT5/gmt-6.5.0-win64.zip DE7E05F87896FFB87E73F24EFB2FE21BE608CDED02AE0C3569652866E1448658

This is the sha256sum from @joa-quim, but the one on the GMT FTP has:

e2253092cea91ce72adf994fdbbb51b2703b3406c2feb36410e79f9e0aac8990  gmt-6.5.0-win64.exe

[PaulWessel]

Not sure how that happened but use @joa-quim's numbers (and even file if in doubt).

[seisman]

I've made the 6.5.0 release at https://github.com/GenericMappingTools/gmt/releases/tag/6.5.0, using @joa-quim's files and sha256sums in https://github.com/GenericMappingTools/gmt/issues/8017#issuecomment-1874444352.

Apprarently, @joa-quim edited the sha256sum numbers yesterday:

e2253092cea91ce72adf994fdbbb51b2703b3406c2feb36410e79f9e0aac8990 is the old sha256sum number. It means the one on the GMT FTP is the old one.

@PaulWessel Please download the latest win64 installers (both the exe and the zip) from https://github.com/GenericMappingTools/gmt/issues/8017#issuecomment-1874444352 and upload them to the FTP server again.

[PaulWessel]

The two Win binary files have been placed in the gmt ftp on SOEST ftp server and should have correct permissions.

[PaulWessel]

I guess next steps are

1. Approve and merge https://github.com/GenericMappingTools/remote-datasets/pull/113.
2. Update oceania server with files from candidate (@PaulWessel or @Esteban82).
3. Website already updated with links to 6.5 so nothing to do there
4. Instagram post announcing 6.5 and massive addition of remote data set (@Esteban82 ?)
5. Twitter (X) post announcing the same things (@maxrjones ?)
6. News item on the Forum Announcement page (@PaulWessel)

[seisman]

FYI, I've uploaded the tarball to Zenodo. The new record is at https://zenodo.org/records/10119499.

[PaulWessel]

I added a news item on the forum under Announcement. Feel free to edit if my links are off...

[Esteban82]

Paul, do you want me to do this?

• Update oceania server with files from candidate

[PaulWessel]

Sure. Forst do a git pull as I have made two changes:

1. Renamed srv_server-release.sh to just server-release.sh (in scripts folder to match the other *-release names)
2. Remove the temporary echo statement that prevents the final command to execute (that ssh on the script in /tmp).

Since you did test-release.sh earlier and this is very similar except using server we should be good to go, and if anything goes wrong we have all the files we need still in candidate. Please go ahead.

[PaulWessel]

So should just be

make server-release

which runs the right script.

[Esteban82]

@PaulWessel I am affraid I can't do it

-bash-4.2$ pwd
/tmp
-bash-4.2$ ls -la release.sh 
-rwx--x--x 1 pwessel gmt 602 ene  7 03:14 release.sh
-bash-4.2$ bash release.sh 
bash: release.sh: Permission denied

[PaulWessel]

Sorry, I need to delete that first. Hold a few seconds.

[PaulWessel]

OK, gone , should work now.

[Esteban82]

Now I could run it.

I am getting a lot of messages like this: I would say that for every directory.

rsync: failed to set times on "/export/gmtserver/gmt/data/server/.": Operation not permitted (1)
rsync: failed to set times on "/export/gmtserver/gmt/data/server/earth": Operation not permitted (1)
rsync: failed to set times on "/export/gmtserver/gmt/data/server/earth/earth_day": Operation not permitted (1)

[PaulWessel]

Yes, I think they are harmless. This is what Ross told me I think: If I (or you) create some files then the other person cannot change permissions etc and get these types of messages. Probably rsync info that gets messed up.

I expect the solution is to have a single user (e.g., gmtdata@soest.hawaii.edu) that we both use when doing server work. In fact, it would be inserted into the various scripts.

I also need to but EarthScope Consortium about taking over the hosting of these data since at some point teh SOEST server will get old and die (and me too!) so then we need to have bus-factor protection for this part of GMT. I will look into who I should contact.

Please check if you see anything funky regarding to permissions on oceania now, and if you can run plots from oceania and not set candidate server first.

[Esteban82]

It finished. This was the last message.

rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1179) [sender=3.1.2]

I test the oceania server and it is working fine.

[PaulWessel]

I am struggling a bit with making a USA map:

gmt grdimage @earth_relief_02m -B -RUS -png map
gmt [WARNING]: gmt_get_dataset_tiles: No earth_relief_02m_p tiles available for your region.
grdimage [ERROR]: Grid x range <= 0.0
grdimage [ERROR]: Make sure west < east for geographic coordinates
grdimage (gmt_api.c:2126(gmtapi_init_grdheader)): Please select compatible -R and -I values
grdimage [WARNING]: Your grid x's or longitudes appear to be outside the map region and will be skipped.
grdimage [WARNING]: No grid or image inside plot domain

but works fine for Argentina, for example.

[Esteban82]

I am struggling a bit with making a USA map:

I can't either. I could with 06m.

gmt grdimage @earth_relief_06m -B -RUS -png map

[Esteban82]

I just made the annoucement on instagram (https://www.instagram.com/p/C10k8Q9MN-m/).

BTW, I think that we should announce also the new remote data sets available. I am thinking that I figure similar to this would be good. Could you do it @PaulWessel ?

https://www.instagram.com/p/CaFJFieLJ2y/?utm_source=ig_web_copy_link&igsh=MzRlODBiNWFlZA==

[Esteban82]

I check it on windows and looks fine.

[remkos]

1. Remko and I could setup a zoom or async work on debugging the dvc issues

Thanks @maxrjones . I just installed the latest dvc with Python 3.12 and it suddenly works. I was not able to get any downloads in the past, despite getting no error message from dvc pull. But as said: this suddenly seems to have repaired itself.

[seisman]

• make announcements on the GMT twitter

Do we still want to do this? I think so, we have more than 1000 followers on Twitter.

[seisman]

Close it if no one cares about Twitter.

[PaulWessel]

Any one care about Must and X? @leouieda, @maxrjones , or @Esteban82 ?

[maxrjones]

Any one care about Must and X? @leouieda, @maxrjones , or @Esteban82 ?

I don't have interest in X

[Esteban82]

Me neither.

[PaulWessel]

OK, whoever wants to can remove the Twitter reminder from our checklist.

[seisman]

OK, whoever wants to can remove the Twitter reminder from our checklist.

Done and pushed directly to the master branch.