Closed michaelgrund closed 6 months ago
Thanks @michaelgrund for keeping track! Ok to open the PRs, but let's wait for a week or two (around mid-Feb) before merging, in case there's some serious bug with PyGMT v0.11.0 and we need to release v0.11.1 to patch it.
Sure @weiji14 , definitely fine for me.
let's wait for a week or two (around mid-Feb) before merging, in case there's some serious bug with PyGMT v0.11.0 and we need to release v0.11.1 to patch it.
We don't have to wait. We can always create a patch release from the v0.11.0 tag if there are any serious bugs.
We don't have to wait. We can always create a patch release from the v0.11.0 tag if there are any serious bugs.
Sure, we can do that, just slightly more work since we need a commit on the main branch, and a backport commit on a patch branch going off from v0.11.0.
Several parameters and a few aliases are deprecated since v0.8.0, v0.9.0 or v0.10.0 and the deprecation warnings need to be removed before release v0.12.0.
This issue is created to track the progress of removing these deprecation warnings:
xshift (X)
andyshift (Y)
(FutureWarning raised since PyGMT v0.8.0) https://github.com/GenericMappingTools/pygmt/pull/3044timestamp (U)
(FutureWarning raised since PyGMT v0.9.0) https://github.com/GenericMappingTools/pygmt/pull/3045Figure.plot
,Figure.plot3d
,Figure.rose
: Remove parametercolor
, usefill
instead (FutureWarning raised since PyGMT v0.8.0) #3032Figure.velo
: #3034uncertaintycolor
, useuncertaintyfill
instead (FutureWarning raised since PyGMT v0.8.0)color
, usefill
insteadFigure.wiggle
: Remove parametercolor
, usefillnegative
orfillpositive
instead (FutureWarning raised since PyGMT v0.8.0) #3035Figure.grdimage
: Remove parameterbit_color
, usebitcolor
instead (Future Warning raised since PyGMT v0.10.0) #3036