Changelog entry for v0.6.0

[maxrjones]

Description of proposed changes

This PR adds a changelog entry for v0.6.0.

Preview: https://pygmt-git-changelog-release-gmt.vercel.app/changes.html

Previous release at #1594

Changelog made by following the instructions at https://github.com/GenericMappingTools/pygmt/blob/main/doc/maintenance.md#updating-the-changelog

TODO:

• Update the DOI badge
• Update citation information https://github.com/GenericMappingTools/pygmt#citing-pygmt
• Add the documentation link https://github.com/GenericMappingTools/pygmt#documentation-for-other-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).

Relates to #1801

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.

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 for drafting this up Meghan (and really sorry for taking up your weekend). This is in pretty good shape already, but I'd like someone else to take a stab at the highlights. It feels like we're underselling what's changed in the past 5 months!

[weiji14]

Putting down Monday here (UTC time) just in case, but I'm hoping to get this over by Sunday in the US if possible.

Suggested change

	## Release v0.6.0 (20YY/MM/DD)
	## Release v0.6.0 (2022/03/14)

[maxrjones]

I think we should edit #1801 to 03/14 to give opportunities for comments at #731 and #1812. It would've been nice to wrap this up today (really missing that extra hour), but a PI day release could also be fun.

[weiji14]

Oo yes, definitely do 3/14! I just realized we'll have 3 new functions (grdhisteq, triangulate, pygmt.datasets.load_sample_data) and 14 inline examples (if we merge in just one of #1719 or #1729) 😆

Edit: And here's a Pi-Day plot adapted from https://www.pygmt.org/v0.5.0/gallery/symbols/text_symbols.html

[maxrjones]

The plot is really nice. Do you mind sharing your code? I'd be interested in trying a couple adjustments.

[maxrjones]

Actually, @weiji14 would you be willing to do the Twitter post for the release? That plot would be great for it 😄

[weiji14]

Sure, I can do the twitter post. I was thinking of putting it in the forum post but couldn't find a good place to put it. The code is:

import pygmt

fig = pygmt.Figure()
fig.basemap(region=[0, 8, 0, 3], projection="X12c/4c", frame=True)

pen = "1.5p"
fig.plot(x=1, y=1.5, style="l3.5c+t3", color="dodgerblue3", pen=pen)
fig.plot(x=2, y=1, style="l3.5c+t.", color="red3", pen=pen)
fig.plot(x=3, y=1.5, style="l3.5c+t1+fCourier-Bold", color="seagreen", pen=pen)
fig.plot(x=4.3, y=1.5, style="l3.5c+t4+fTimes-Italic", color="gold", pen=pen)
fig.plot(x=5.6, y=1.5, style="l3.5c+t1+fBookman-Light", color="pink", pen=pen)
fig.plot(x=7, y=1.5, style="l3.5c+t\160+fSymbol,darkorange", color="magenta4", pen=pen)

fig.show()

[maxrjones]

This is in pretty good shape already, but I'd like someone else to take a stab at the highlights. It feels like we're underselling what's changed in the past 5 months!

I agree. @willschlitzer, do you have any thoughts on the highlights? I know some of your implemented features are still pending (sorry for the slow reviews), but since you've put a lot of work in since the last release it would be great to get your opinions on this.

[willschlitzer]

This is in pretty good shape already, but I'd like someone else to take a stab at the highlights. It feels like we're underselling what's changed in the past 5 months!

I agree. @willschlitzer, do you have any thoughts on the highlights? I know some of your implemented features are still pending (sorry for the slow reviews), but since you've put a lot of work in since the last release it would be great to get your opinions on this.

Looks good to me! Only change I would consider is that dataset loading function under the highlights section instead of the new feature: I think that's a pretty big (and positive!) change.

[weiji14]

Ok from me, but ping @GenericMappingTools/pygmt-maintainers for a second (or third) approval.

[michaelgrund]

Except the minor typo, everything looks great! Thanks everybody.