Release PyGMT v0.3.1

[willschlitzer]

Release: v0.3.1
Scheduled Date: 2021/03/14
Pull request due date: 2021/03/12

Priority PRs/issues to complete prior to release
@GenericMappingTools/python Any priorities to finish for this patch release?

• Unnecessary files in the source distributions (Unnecessary files in the source distribution? #904)
• Document how to skip CI in the contributing guides (Document how to skip CI in the contributing guides #908)
• Better categories for gallery examples (Better categories for gallery examples #876)
• Let pygmt.info load datetime columns into a str dtype array (Let pygmt.info load datetime columns into a str dtype array #960)

Before release:

• Reserve a DOI on Zenodo by clicking on "New Version"
• Finish up 'Changelog entry for v0.3.1' Pull Request (Changelog entry for v0.3.1 release #1047):
  • Add a new entry in doc/_static/version_switch.js for documentation switcher
  • Update citation information https://github.com/GenericMappingTools/pygmt#citing-pygmt
  • Add the documentation link https://github.com/GenericMappingTools/pygmt#documentation-for-other-versions
  • Add compatibility information https://github.com/GenericMappingTools/pygmt#compatibility-with-python-and-gmt-versions
  • Copy draft changelog from Release Drafter and edit it to look nice

Release:

• At the PyGMT release page on GitHub:
  • Edit the draft release notes with the finalized changelog
  • Set the tag version and release title to v0.3.1
  • Make a release by clicking the 'Publish Release' button, this will automatically create a tag too
• Manually upload the pygmt-v0.3.1.zip file to https://zenodo.org/deposit, ensure that it is filed under the correct reserved DOI

After release:

• Update conda-forge pygmt-feedstock [Usually done automatically by conda-forge's bot]
• Bump PyGMT version on https://github.com/GenericMappingTools/try-gmt
• Announce the release on:
  • GMT forum
  • [Major/Minor releases only] GMT website (News)
  • ResearchGate
  • Twitter

---

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

[weiji14]

Alright, since we're getting close to the release date, I've moved a couple of lower priority issues from the v0.3.1 to v0.4.0 milestone. We should definitely prioritize wrapping up the gallery reorganization #876 in the next day or two (since a few other PRs depend on it). I'd encourage everyone to help out in reviewing the open PRs, and I see that quite a few people have stepped up which is good!

Afterwards, on 14 March (UTC), we'll need volunteers to help out with the following:

• Start a PR for a new Changelog entry (see previous one at Changelog entry for v0.3.0 #887 and instructions at https://github.com/GenericMappingTools/pygmt/blob/master/MAINTENANCE.md#making-a-release
• Draft a release announcement for the forum at https://hackmd.io/@pygmt (see previous one at https://hackmd.io/@pygmt/v0-3-0_announcement)
• Social media outreach:
  • Setup Twitter/Instagram as mentioned in the last release at Release PyGMT v0.3.0 #845 (comment)
  • If anyone has experience with writing a blog post, that would be a great contribution too!
  • Any contributor wanting to be listed as a collaborator on PyGMT's ResearchGate profile, just ping me (or any other @GenericMappingTools/python member) and we'll get you added in.

Just raise your hand 👋 up on what you'd like to help out with and you'll get the job. No interview required.

[willschlitzer]

I'll do the change log. I can do the release (AKA push the green button) as well unless someone else wants to!

[willschlitzer]

@weiji14 Do we have a Zenodo DOI yet?

[core-man]

• Any contributor wanting to be listed as a collaborator on PyGMT's ResearchGate profile, just ping me (or any other @GenericMappingTools/python member) and we'll get you added in.

@weiji14 I am grateful to be listed as a collaborator.

[weiji14]

@weiji14 Do we have a Zenodo DOI yet?

Yep, the DOI for v0.3.1 will be 10.5281/zenodo.4592991.

@weiji14 I am grateful to be listed as a collaborator.

Cool, just followed you on ResearchGate, you'll need to follow me back for me to add you as a collaborator according to https://www.researchgate.net/post/how_can_I_add_collaborators_to_an_existing_project (Same for anyone else wanting to join).

[michaelgrund]

Alright, since we're getting close to the release date, I've moved a couple of lower priority issues from the v0.3.1 to v0.4.0 milestone. We should definitely prioritize wrapping up the gallery reorganization #876 in the next day or two (since a few other PRs depend on it). I'd encourage everyone to help out in reviewing the open PRs, and I see that quite a few people have stepped up which is good!

Afterwards, on 14 March (UTC), we'll need volunteers to help out with the following:

* [ ]  Start a PR for a new Changelog entry (see previous one at #887 and instructions at https://github.com/GenericMappingTools/pygmt/blob/master/MAINTENANCE.md#making-a-release

* [ ]  Draft a release announcement for the forum at https://hackmd.io/@pygmt (see previous one at https://hackmd.io/@pygmt/v0-3-0_announcement)

* [ ]  Social media outreach:
  
  * [ ]  Setup Twitter/Instagram as mentioned in the last release at [#845 (comment)](https://github.com/GenericMappingTools/pygmt/issues/845#issuecomment-779489746)
  * [ ]  If anyone has experience with writing a blog post, that would be a great contribution too!
  * [ ]  Any contributor wanting to be listed as a collaborator on [PyGMT's ResearchGate profile](https://www.researchgate.net/project/PyGMT-A-Python-interface-for-the-Generic-Mapping-Tools), just ping me (or any other @GenericMappingTools/python member) and we'll get you added in.

Just raise your hand 👋 up on what you'd like to help out with and you'll get the job. No interview required.

I will only be partially available on 14 March, however, if possible I could help out with updating the website etc. (as for the last release).

[maxrjones]

Alright, since we're getting close to the release date, I've moved a couple of lower priority issues from the v0.3.1 to v0.4.0 milestone. We should definitely prioritize wrapping up the gallery reorganization #876 in the next day or two (since a few other PRs depend on it). I'd encourage everyone to help out in reviewing the open PRs, and I see that quite a few people have stepped up which is good!

Afterwards, on 14 March (UTC), we'll need volunteers to help out with the following:

* [ ]  Start a PR for a new Changelog entry (see previous one at #887 and instructions at https://github.com/GenericMappingTools/pygmt/blob/master/MAINTENANCE.md#making-a-release

* [ ]  Draft a release announcement for the forum at https://hackmd.io/@pygmt (see previous one at https://hackmd.io/@pygmt/v0-3-0_announcement)

* [ ]  Social media outreach:
  
  * [ ]  Setup Twitter/Instagram as mentioned in the last release at [#845 (comment)](https://github.com/GenericMappingTools/pygmt/issues/845#issuecomment-779489746)
  * [ ]  If anyone has experience with writing a blog post, that would be a great contribution too!
  * [ ]  Any contributor wanting to be listed as a collaborator on [PyGMT's ResearchGate profile](https://www.researchgate.net/project/PyGMT-A-Python-interface-for-the-Generic-Mapping-Tools), just ping me (or any other @GenericMappingTools/python member) and we'll get you added in.

Just raise your hand 👋 up on what you'd like to help out with and you'll get the job. No interview required.

Since I previously said I would, I can create a twitter account and then hopefully transfer it later on to someone who understands how to use emojis. Instagram is over my head though, sorry. Do you think GMT/PyGMT twitter should be the same or different?

[core-man]

I am available, but I am not good at social media outreach. Maybe I can help draft a release announcement for the forum at https://hackmd.io/@pygmt if it does not need any permission.

[willschlitzer]

Alright, since we're getting close to the release date, I've moved a couple of lower priority issues from the v0.3.1 to v0.4.0 milestone. We should definitely prioritize wrapping up the gallery reorganization #876 in the next day or two (since a few other PRs depend on it). I'd encourage everyone to help out in reviewing the open PRs, and I see that quite a few people have stepped up which is good!
Afterwards, on 14 March (UTC), we'll need volunteers to help out with the following:

* [ ]  Start a PR for a new Changelog entry (see previous one at #887 and instructions at https://github.com/GenericMappingTools/pygmt/blob/master/MAINTENANCE.md#making-a-release

* [ ]  Draft a release announcement for the forum at https://hackmd.io/@pygmt (see previous one at https://hackmd.io/@pygmt/v0-3-0_announcement)

* [ ]  Social media outreach:
  
  * [ ]  Setup Twitter/Instagram as mentioned in the last release at [#845 (comment)](https://github.com/GenericMappingTools/pygmt/issues/845#issuecomment-779489746)
  * [ ]  If anyone has experience with writing a blog post, that would be a great contribution too!
  * [ ]  Any contributor wanting to be listed as a collaborator on [PyGMT's ResearchGate profile](https://www.researchgate.net/project/PyGMT-A-Python-interface-for-the-Generic-Mapping-Tools), just ping me (or any other @GenericMappingTools/python member) and we'll get you added in.

Just raise your hand 👋 up on what you'd like to help out with and you'll get the job. No interview required.

Since I previously said I would, I can create a twitter account and then hopefully transfer it later on to someone who understands how to use emojis. Instagram is over my head though, sorry. Do you think GMT/PyGMT twitter should be the same or different?

Unfortunately "@pygmt" on Twitter is a suspended account; I think keeping PyGMT the same as the GMT Twitter is fine for now; I don't foresee the project tweeting that often.

Also, I registered "pygmt.dev@gmail.com" (pygmt@gmail.com was too short) if we want to start up a YouTube channel for tutorials and the like.

[weiji14]

I am available, but I am not good at social media outreach. Maybe I can help draft a release announcement for the forum at https://hackmd.io/@pygmt if it does not need any permission.

Cool, just sent a hackmd invite to you and @michaelgrund too. I think most everybody is in but let me know if anyone else wants to join.

Since I previously said I would, I can create a twitter account and then hopefully transfer it later on to someone who understands how to use emojis. Instagram is over my head though, sorry. Do you think GMT/PyGMT twitter should be the same or different?

Unfortunately "@pygmt" on Twitter is a suspended account; I think keeping PyGMT the same as the GMT Twitter is fine for now; I don't foresee the project tweeting that often.

Also, I registered "pygmt.dev@gmail.com" (pygmt@gmail.com was too short) if we want to start up a YouTube channel for tutorials and the like.

Thanks @willschlitzer for setting that up! I agree that using the same twitter handle for GMT/PyGMT is fine, people can always hashtag #pygmt to be more specific. Probably easier to use the GMT YouTube channel to post PyGMT content, but I'm sure we'll find a use for that email at some point.

[maxrjones]

We're live on twitter! https://twitter.com/gmt_software

The 'handle' has to be 4+ characters (not GMT), less than 15 characters (not GenericMappingTools), and only alphanumeric characters and underscores. I came up with @gmt_software but if anyone has better ideas please feel free to share.

[seisman]

The 'handle' has to be 4+ characters (not GMT), less than 15 characters (not GenericMappingTools),

It's really annoying 🤦