[maxrjones]

Description of proposed changes

This PR adds the changelog entry for v0.9.0.

Preview at https://pygmt-dev--2469.org.readthedocs.build/en/2469/changes.html

Related to issue #2424

Previous release v0.8.0 at #2272

TODO

• Copy the draft release note from https://github.com/GenericMappingTools/pygmt/releases to doc/changes.md
• Update the DOI badge
• Update citation information https://github.com/GenericMappingTools/pygmt#citing-pygmt and CITATION.cff
• Add the version to the compatibility table https://github.com/GenericMappingTools/pygmt#compatibility-with-gmtpythonnumpy-versions
• Add highlights
• Update with any remaining PRs merged before release
• Edit the change list to remove any trivial changes (updates to the README, typo fixes, CI configuration, etc)
• Edit the list of people who contributed to the release, linking to their GitHub account. Sort their names by the number of commits made since the last release (e.g., use git shortlog HEAD...v0.1.2 -sne).

Fixes #

Reminders

• Run make format and make check to make sure the code follows the style guide.
• Add tests for new features or tests that would have caught the bug that you're fixing.
• Add new public functions/methods/classes to doc/api/index.rst.
• Write detailed docstrings for all functions/methods.
• If wrapping a new module, open a 'Wrap new GMT module' issue and submit reasonably-sized PRs.
• If adding new functionality, add an example to docstrings or tutorials.
• Use underscores (not hyphens) in names of Python files and directories.

Slash Commands

You can write slash commands (/command) in the first line of a comment to perform
specific operations. Supported slash commands are:

• /format: automatically format and lint the code
• /test-gmt-dev: run full tests on the latest GMT development version

[weiji14]

Thanks @maxrjones! Hopefully someone can take another look before we merge this. I've got a crazy weekend schedule, but will try to help out as much as I can on Monday NZ time (which is practically Sunday UTC).

[maxrjones]

Thanks @maxrjones! Hopefully someone can take another look before we merge this. I've got a crazy weekend schedule, but will try to help out as much as I can on Monday NZ time (which is practically Sunday UTC).

I put March 31 on the release issue, but if you prefer we wait until Sunday UTC (April 02) that's totally fine with me. I could update the dates in this PR. I originally suggested Friday expecting to be away this weekend, but that's actually not the case.

[seisman]

Looks good to me except minor edits.

[maxrjones]

The last couple commits have led to failures on the windows CI. Does anyone know if those are a barrier to releasing on this commit?

[weiji14]

The last couple commits have led to failures on the windows CI. Does anyone know if those are a barrier to releasing on this commit?

Seems to be just on the WIndows - Python 3.8 build. Let's try a simple re-run first in case it's just a random failure.

[weiji14]

Ok, builds pass now. Feel free to ship it @maxrjones 🚀🚀🚀