Release PyGMT 0.1.1

[seisman]

Release: v0.1.1
Scheduled Date: 2020/05/XX

Before release:

• Reserve a DOI on Zenodo (@leouieda @seisman)
• Update Changelog (@weiji14) (Changelog entry for v0.1.1 #445)

Release:

• Make a tag and push it to github

git tag x.x.x
git push --tags

• Go to GitHub Release and make a release
• Announce release on the GMT forum and website (News)

After release:

• Create branch 0.x for bug-fixes if this is a minor release (i.e. create branch 0.1 after 0.1.0 is released)
• Commit changes to Github

3rd party update:

• Update conda-forge pygmt-feedstock (@moorepants)

---

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

[weiji14]

Cool, I'll start working on the changelog. It's at #445.

[weiji14]

Alright, changelog is done. Would you like to make the tag @seisman?

[seisman]

@weiji14 Is the tag 0.1.1 or v0.1.1?

[weiji14]

v0.1.1

[seisman]

Done with the tagging.

[weiji14]

Cool, I'll make the release and handle the Zenodo part. Do you want to work on the conda package?

[seisman]

OK, I'll open a PR for the conda package.

[weiji14]

Sigh, got the wrong Zenodo DOI again. I'm going to manually republish it...

[seisman]

Wrong DOI in PR #445?

[weiji14]

No, it's complicated. We should turn off Zenodo automatically creating a DOI when we publish a release because it won't use the reserved one. Will have to manually update instead, but at least it means we can put the DOI in the changelog before the release.

[weiji14]

Ok, the DOI in #445 works - now. I'll update the instructions on #446 with the steps to take. Edit, done at f2842c0.

[seisman]

@weiji14 Could you post an announcement on the GMT forum so that we can finish the release? You're definitely a better news writer than me! 😄

I'm not sure if it's necessary to add the new release to the news on the GMT website, as we definitely will release frequently in the future, then PyGMT releases may take up the whole list of recent news.

[weiji14]

@weiji14 Could you post an announcement on the GMT forum so that we can finish the release? You're definitely a better news writer than me! smile

Ok cool, I'll do that in a bit, just want to finish off preparing a plot for a group meeting later (made using PyGMT of course).

I'm not sure if it's necessary to add the new release to the news on the GMT website, as we definitely will release frequently in the future, then PyGMT releases may take up the whole list of recent news.

Yeah, let's stick to announcing minor releases (e.g. 0.1.0, 0.2.0).

[weiji14]

Ok, announcement made on the forum, see https://www.generic-mapping-tools.org) (News) (https://forum.generic-mapping-tools.org/t/pygmt-v0-1-1-released! Would be great to update it on ResearchGate as well https://www.researchgate.net/project/PyGMT-A-Python-interface-for-the-Generic-Mapping-Tools for more visibility.

[seisman]

@weiji14 Great!

Would be great to update it on ResearchGate as well https://www.researchgate.net/project/PyGMT-A-Python-interface-for-the-Generic-Mapping-Tools for more visibility.

I agree. I just added an update for PyGMT v0.1.1 (+v0.1.0). It seems I can't add you to collaborators, even though I can find you on RG. Perhaps only @leouieda can do that?