Release GMT 6.5.0 - Githubissues

PaulWessel commented 10 months ago

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!)

Esteban82 commented 10 months ago

When we update/release the new remote datasets?

PaulWessel commented 10 months ago

Yes, we should be able to release the datasets the same day.

PaulWessel commented 10 months ago

We should probably add a tickbox for "Updating all new remove data to main oceania server".

PaulWessel commented 10 months ago

I suggest we aim for 6.5 release on Dec 1, otherwise we'll not get there in 2023. I know there are outstanding issues with bugs but there always are. No way to fix everything unfortunately. We can always to a 6.5.1 if there are good reasons after fixing some bugs. @maxrjones, might you be able to help with the ChangeLog again?