Release PyGMT 0.2.0

[weiji14]

Release: v0.2.0
Scheduled Date: 2020/09/12

Before release:

• Reserve a DOI on Zenodo by clicking on "New Version"
• Update Changelog (Changelog entry for v0.2.0 #599)

Release:

• Make a tag and push it to Github
• 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] pygmt v0.2.0 conda-forge/pygmt-feedstock#8
• Bump PyGMT version on https://github.com/GenericMappingTools/try-gmt
• Announce the release on:
  • GMT forum (https://forum.generic-mapping-tools.org/t/pygmt-v0-2-0-released/879)
  • GMT website (News) Add the news for PyGMT v0.2.0 website#69
  • ResearchGate (link)
• 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

---

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

[weiji14]

Scheduling this release tentatively for Thursday 10 Sep 2020 (UTC time), since Monday is a public holiday in the US. Below is a list of outstanding PRs, please let us know if there's anything that should be prioritized for the next few days (e.g. it would help with your research/day-job), and we can try to re-arrange some things (on a best effort basis).

Essential bugfix 🪲 PRs for this release, which we should try our best to do:

• WIP: Update 6 baseline images due to GMT 6.1.0 changes #522 Update 6 baseline images due to GMT 6.1.0 changes (if not too much work)
• Ensure plotting xarray grids with different central meridians work on some projections #560 Ensure plotting xarray grids with different central meridians work, though we won't resolve Cylindrical projections 'Q' plot incorrectly in pygmt when using xarrays #390 properly yet
• Add a test for xarray shading #581 Add a test for xarray shading

Nice to have enhancements ✨, can wait for next patch release (v0.2.1), or get into v0.2.0 if someone reviews/approves them 😄:

• Add tutorial for pygmt.Figure.text #480 Add tutorial for pygmt.Figure.text
• Add tutorial for pygmt.config #482 Tutorial covering pygmt.config
• Refactor text to use virtualfile_from_vectors instead of pandas tempfile #559 Refactor text to use virtualfile_from_vectors instead of pandas tempfile (note: this didn't fix Figure.text: Allow passing in a list/array of angle/font/justify values to text #483)
• Allow pandas.DataFrame table and 1D/2D numpy array inputs into pygmt.info #574 Allow pandas.DataFrame table inputs into pygmt.info
• Sensible array outputs for pygmt info #575 Sensible array outputs for pygmt info
• RFC Allow for io.StringIO inputs to certain modules #576 Allow for io.StringIO inputs to certain modules

New features to push ⏩ to next minor release (v0.3.0):

• Wrap subplot #412 Wrap subplot
• Wrap plot3d #471 Wrap plot3d
• Wrap velo #525 Add velo function

CC @GenericMappingTools/python-contributors, @lhoupert, @hemmelig, @MarkWieczorek, @EJFielding and anyone else interested.

[seisman]

@weiji14 The test test_grdview_grid_file_with_region_subset is marked as xfail, but it actually passes. You may want to check it if it really works as expected.

[weiji14]

Gonna bump this out by a day to Friday 11 Sep 2020 (UTC time). Should be possible to get #560 and #581 done today, but the release note curation will take a bit of time.

[leouieda]

@weiji14 thanks for leading the charge on this! 👏🏽

A few suggestions to simplify this:

• You don't need to create the tag locally. When you make the GitHub release, it will make the tag automatically as well so that's one less thing to do.
• The perks of not being 1.0 yet is that we don't have to worry about backporting bug fixes to previous releases. So there is no need for a 0.1 branch, which makes things so much simpler.

[weiji14]

@weiji14 thanks for leading the charge on this! 👏🏽

Welcome, hope you and your partner are doing well with the new little one 😁

A few suggestions to simplify this:

• You don't need to create the tag locally. When you make the GitHub release, it will make the tag automatically as well so that's one less thing to do.

• The perks of not being 1.0 yet is that we don't have to worry about backporting bug fixes to previous releases. So there is no need for a 0.1 branch, which makes things so much simpler.

Sounds good, we can update the release checklist template to remove these two bullet points. Also ties in with your previous comment at #424 (comment).

[weiji14]

Ok, release time! @seisman, could you do the Github Release at https://github.com/GenericMappingTools/pygmt/releases (which will make the tag v0.2.0 as @leouieda menitoned), then I'll upload the zip file to Zenodo.

[seisman]

Done.

[weiji14]

Thanks @seisman, I see you've bumped up the PyGMT version at try-gmt (GenericMappingTools/try-gmt@2f22696). I've just made the PyGMT v0.2.0 release announcement on the forum at https://forum.generic-mapping-tools.org/t/pygmt-v0-2-0-released/879 too.

So what's left should be to link to that on the website, and also on ResearchGate. How about you pick one and I'll do the other?

[seisman]

OK, I'll update the website.

[weiji14]

Great, announcements all done! We can close this now and move on to the next big thing 😁