-
Notifications
You must be signed in to change notification settings - Fork 215
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
Policy for minimum supported GMT versions #2967
Comments
We can probably support about 2-3 minor GMT versions at a time, so maybe go with Option 2 (drop GMT versions after 3 years)? That's assuming that GMT continues to have a minor release every year, which means PyGMT will support at least 2 (or more) GMT minor versions at a time. |
I'm also in favor of option 2. Ping @GenericMappingTools/pygmt-maintainers for comments. |
Ping @yvonnefroehlich @willschlitzer @michaelgrund for comments. Otherwise, we will go with option 2. |
I feel PyGMT should support the last 2-3 GMT versions. From my experience, many users are not updating GMT immediately after a new release. I personally prefer to stay with the same GMT version for a publication, which can easily take a year (or more) to be finally published. So, I think option 2 is a fair compromise between supporting older GMT versions and the work for developers and maintainers. |
With GMT 6.5.0 released, now PyGMT supports three GMT minor versions, 6.3, 6.4 and 6.5, although old GMT versions may have some bugs and miss some features. Supporting multiple GMT versions is a big burden for us maintainers, so we need to decide our policy for the minimum supported GMT versions.
Here are a few options:
FYI, GMT usually has one release per year (https://github.com/GenericMappingTools/gmt/tags).
The text was updated successfully, but these errors were encountered: