Skip to content

Remove the deprecated parameter and alias names in v0.12.0 #3033

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
6 tasks done
michaelgrund opened this issue Feb 2, 2024 · 4 comments
Closed
6 tasks done

Remove the deprecated parameter and alias names in v0.12.0 #3033

michaelgrund opened this issue Feb 2, 2024 · 4 comments
Labels
deprecation Deprecating a feature
Milestone

Comments

@michaelgrund
Copy link
Member

michaelgrund commented Feb 2, 2024

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:

@weiji14
Copy link
Member

weiji14 commented Feb 2, 2024

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.

@michaelgrund
Copy link
Member Author

Sure @weiji14 , definitely fine for me.

@michaelgrund michaelgrund changed the title Remove the deprecated parameter and alias names in v0.12.0 (deprecated since v0.8.0) Remove the deprecated parameter and alias names in v0.12.0 Feb 2, 2024
@seisman
Copy link
Member

seisman commented Feb 2, 2024

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.

@weiji14
Copy link
Member

weiji14 commented Feb 2, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deprecation Deprecating a feature
Projects
None yet
Development

No branches or pull requests

3 participants