Conversation
9383f41 to
2c8eb47
Compare
doc/changes.md
Outdated
|
|
||
| ### Enhancements | ||
|
|
||
| * pygmt.x2sys_cross: Refactor to use virtualfiles for output tables [BREAKING CHANGE: Dummy times in 3rd and 4th columns now have np.timedelta64 type] ([#3182](https://github.com/GenericMappingTools/pygmt/pull/3182)) |
There was a problem hiding this comment.
Perhaps we should add a separate category for breaking changes?
There was a problem hiding this comment.
Would make those changes more / directly visible to users!
Meaning we have to define a new label "breaking changes" and add it to
pygmt/.github/release-drafter.yml
Lines 8 to 20 in 6dc8eb0
There was a problem hiding this comment.
Common changelog uses a prefix like **Breaking** or **<subsystem> (breaking):** for highlighting breaking changes, see https://github.com/vweevers/common-changelog?tab=readme-ov-file#244-prefixes. Maybe we could follow that instead of adding a new label/section?
| family-names: Wessel | ||
| affiliation: University of Hawaiʻi at Mānoa, USA | ||
| orcid: https://orcid.org/0000-0001-5708-7336 |
There was a problem hiding this comment.
Didn't want to bring this up so soon, but since Paul passed away, I'm wondering what the convention was in keeping his name on the citation list? Do we remove his name now, keep his name on for a couple more releases, or remove it after his funding/grants run out? See e.g. https://academia.stackexchange.com/questions/116845/dead-author-ethical-guidelines
There was a problem hiding this comment.
Personally, I prefer to keep Paul's name at least in the period of the funding.
The link you provided only discussed the topic for journal articles, but here it's software and may be slightly different.
Anyway, we should keep this in mind and may need to revisit it later.
Edit: Probably should ask for comments from the GMT steering community. Will do it later.
Co-authored-by: Yvonne Fröhlich <94163266+yvonnefroehlich@users.noreply.github.com>
|
This PR is ready for final review. I plan to merge this PR and make the release in 12 hours (before midnight for UTC+8 time zone). |
doc/changes.md
Outdated
| * SPEC 0: Bump minimum supported version to xarray 2022.09 ([#3372](https://github.com/GenericMappingTools/pygmt/pull/3372)) | ||
| * SPEC 0: Bump minimum supported version to NumPy 1.24+ ([#3286](https://github.com/GenericMappingTools/pygmt/pull/3286)) |
There was a problem hiding this comment.
These should go under 'Deprecations' I think. We used to classify the NEP29 PRs as 'deprecations' (e.g. at https://www.pygmt.org/v0.12.0/changes.html#release-v0-11-0-2024-02-01), but somehow put the SPEC 0 PRs under 'maintenance' in Release v0.12.0. Probably should move them all to Deprecations.
Co-authored-by: Wei Ji <23487320+weiji14@users.noreply.github.com>
weiji14
left a comment
There was a problem hiding this comment.
Looks good to me! Wait for second approval before merge.
Co-authored-by: Michael Grund <23025878+michaelgrund@users.noreply.github.com>
Co-authored-by: Yvonne Fröhlich <94163266+yvonnefroehlich@users.noreply.github.com>
Co-authored-by: Michael Grund <23025878+michaelgrund@users.noreply.github.com>
Description of proposed changes
This PR adds the changelog entry for v0.13.0.
Checklist
doc/_static/version_switch.jsfor documentation switcherdoc/minversions.mdCITATION.cffand BibTeX at https://github.com/GenericMappingTools/pygmt#citing-pygmtdoc/changes.mddoc/changes.mdgit shortlog HEAD...v0.1.2 -sne)