# [PyGMT v0.3.0 released](https://forum.generic-mapping-tools.org/t/pygmt-v0-3-0-released)

**Announcing [PyGMT v0.3.0](https://github.com/GenericMappingTools/pygmt/releases/tag/v0.3.0), now with functions for making [inset](https://www.pygmt.org/v0.3.0/tutorials/inset.html) and [subplot](https://www.pygmt.org/v0.3.0/tutorials/subplots.html) maps!**

The PyGMT team is thrilled to present version [v0.3.0](https://www.pygmt.org/v0.3.0), a release that packs a great punch! Some of the highlights for this release include:

* Wrap inset ([#788](https://github.com/GenericMappingTools/pygmt/pull/788)) for making overview maps, and subplot ([#822](https://github.com/GenericMappingTools/pygmt/pull/822)) for multi-panel figures
* Apply standardized formatting conventions ([#775](https://github.com/GenericMappingTools/pygmt/pull/775)) across most documentation pages
* Drop Python 3.6 support ([#699](https://github.com/GenericMappingTools/pygmt/pull/699)) so PyGMT now requires Python 3.7 or newer

The full list of changes can be found in the [changelog](https://www.pygmt.org/v0.3.0/changes.html#release-v0-3-0-2021-02-15). Installation instructions can be found at https://www.pygmt.org/v0.3.0/install.html, or you can try it online first at [try-gmt](https://github.com/GenericMappingTools/try-gmt)! Our new maintainer @willschlitzer has done a great job wrapping new functions like [grd2cpt](https://www.pygmt.org/v0.3.0/api/generated/pygmt.grd2cpt.html) while increasing the number of [walkthrough tutorials](https://www.pygmt.org/v0.3.0/tutorials)! Cheers too to new contributors [@michaelgrund](https://github.com/michaelgrund) for making multiple new [gallery examples on plotting map items](https://www.pygmt.org/v0.3.0/gallery/index.html#plotting-map-items), and to our GMT postdoc @meghanj who's done a thorough review of our plotting documentation at [#881](https://github.com/GenericMappingTools/pygmt/pull/881) and helped out with setting up the PyGMT Devs Slack channel and so much more!

Since it's a really big release this time around, we encourage you to explore the main changes visually at the PyGMT [gallery](https://www.pygmt.org/v0.3.0/gallery/index.html) and [tutorials](https://www.pygmt.org/v0.3.0/tutorials/index.html) page!

[](https://www.pygmt.org/v0.3.0/gallery/index.html#plotting-map-items)

### :railway_track: Roadmap to [v0.4.0](https://github.com/GenericMappingTools/pygmt/milestone/6)

To keep the momentum going, here's what we have planned for the next release (some which we need help with!):

- Integration with geopandas to plot shapely geometries ([#608](https://github.com/GenericMappingTools/pygmt/issues/608))
- Wrap more GMT modules e.g. velo ([#525](https://github.com/GenericMappingTools/pygmt/pull/525)), xyz2grd ([#636](https://github.com/GenericMappingTools/pygmt/pull/636)), triangulate ([#731](https://github.com/GenericMappingTools/pygmt/pull/731)), solar ([#804](https://github.com/GenericMappingTools/pygmt/pull/804)), rose ([#794](https://github.com/GenericMappingTools/pygmt/pull/794)) and histogram ([#593](https://github.com/GenericMappingTools/pygmt/issues/563))
- Improve the `Figure.show()` method for displaying previews ([#529](https://github.com/GenericMappingTools/pygmt/pull/529))
- `Figure.hlines()` and `Figure.vlines()` for plotting horizontal and vertical lines ([#670](https://github.com/GenericMappingTools/pygmt/issues/670))

### :warning: Deprecation warnings

To keep in line with the rest of the scientific software stack and ensure a relatively bug-free product, we will *likely* be dropping support for some packages in the next minor (PyGMT v0.4.0) release, so make sure you keep things up to date!

- Drop Numpy<=1.16 as per [NEP 29 — Recommend Python and Numpy version support as a community policy standard](https://numpy.org/neps/nep-0029-deprecation_policy.html), see issue [#690](https://github.com/GenericMappingTools/pygmt/issues/690)
- Potentially drop GMT 6.1.1, so that GMT 6.2.0 is required for PyGMT v0.4.0 (though this is up for discussion).

The compatibility matrix will be listed on https://www.pygmt.org/dev/#compatibility-with-python-and-gmt-versions so keep an eye out!

### :two_women_holding_hands: Call for contributors

Contributing means so much more than writing code! We need help with outreach, documentation, and maintenance as well. We are keen on growing a more diverse :rainbow: and international :earth_africa: community, and these are stuff that are in the pipeline:

- [Design a fresh new PyGMT logo!](https://forum.generic-mapping-tools.org/t/design-for-pygmt-logo)
- [PyGMT tutorial at SciPy 2021](https://github.com/GenericMappingTools/scipy2021) (12-13 July 2021) - submission proposal is being finalized today and we'll need help with making Jupyter notebooks in the coming months
- [Outreachy remote internships for supporting diversity](https://github.com/GenericMappingTools/pygmt/issues/715) (~Aug/Sep 2021) - need funding/volunteers/people good at proposal writing
- More PyGMT community meetings online! See e.g. the last one held on [early Feb 2021](https://forum.generic-mapping-tools.org/t/pygmt-community-zoom-meeting-friday-5-feb-2021-utc-1700). We'll look into doing more before each PyGMT release (quarterly?).
- Writing up a PyGMT paper (see [#677](https://github.com/GenericMappingTools/pygmt/issues/677)) sometime in 2021/2022.

Don't know where to start? Go to https://github.com/GenericMappingTools/pygmt/contribute or reach out to us here on the forum (now with a dedicated [PyGMT subsection](https://forum.generic-mapping-tools.org/c/questions/pygmt-q-a))!

Enjoy :partying_face: