Release PyGMT 0.2.1

Release: v0.2.1 Scheduled Date: 2020/11/14

Before release:

• Reserve a DOI on Zenodo by clicking on “New Version”
• Update Changelog (#683)
• Add a new entry in doc/_static/version_switch.js for documentation switcher (#683)
• Update citation information https://github.com/GenericMappingTools/pygmt#citing-pygmt (#683)

Release:

• Go to GitHub Release and make a release, this will automatically create a tag too
• Manually upload the pygmt-vX.Y.Z.zip file to https://zenodo.org/deposit, make sure you file it under the correct reserved DOI

After release:

• Update conda-forge pygmt-feedstock [Usually done automatically by conda-forge’s bot] (https://github.com/conda-forge/pygmt-feedstock/pull/11)
• Bump PyGMT version on https://github.com/GenericMappingTools/try-gmt (https://github.com/GenericMappingTools/try-gmt/pull/13)
• Announce the release on:
  • GMT forum https://forum.generic-mapping-tools.org/t/pygmt-v0-2-1-released/1038/1
  • [Major/Minor releases only] GMT website (News)
  • ResearchGate
  • Twitter (https://twitter.com/leouieda/status/1328759813732405248)

---

• Party 🎉 (don’t tick before all other checkboxes are ticked!)

[weiji14]

Thanks for making the tweet @leouieda! It really helps to spread the word outside of our GIthub bubble.

And yes, this probably should have been v0.3.0 as per semantic versioning. The ‘bulk’ of the release was mostly documentation changes, with new features (plot3d and Python 3.9 support) kinda slipped in towards the end because we ‘might as well’. Will keep this in mind for the next release.

[weiji14]

shall we do a tweet as well?

There is no official Twitter account for GMT yet, but see the proposal of an Instagram account (https://forum.generic-mapping-tools.org/t/1011/3).

I was actually hinting @leouieda to do a tweet for us (like https://twitter.com/leouieda/status/1305805309374590976 for PyGMT v0.2.0). An official social media account (Twitter, Instagram, etc) sounds good but let’s discuss it in the meeting next week.