Changelog entry for v0.3.0 #887
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| @@ -1,6 +1,111 @@ | ||||||||||||||||||||||||||||||||||
| Changelog | ||||||||||||||||||||||||||||||||||
| ========= | ||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||
| Release v0.3.0 (2021/02/15) | ||||||||||||||||||||||||||||||||||
| --------------------------- | ||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||
| .. image:: https://zenodo.org/badge/DOI/10.5281/zenodo.4522136.svg | ||||||||||||||||||||||||||||||||||
| :alt: Digital Object Identifier for the Zenodo archive | ||||||||||||||||||||||||||||||||||
| :target: https://doi.org/10.5281/zenodo.4522136 | ||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||
| Highlights | ||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||
| * | ||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||
| * | |
| * 🎉 **Third minor release of PyGMT** 🎉 | |
| * Wrap inset (#788) for making overview maps and subplot (#822) for multi-panel figures | |
| * Apply standardized formatting conventions (#775) across most documentation pages | |
| * Drop Python 3.6 support (#699) so PyGMT now requires Python 3.7 or newer |
Feel free to suggest edits in the wording. I'm also thinking whether to mention the upcoming drop in support for GMT 6.1.1 (once GMT 6.2.0 is out, something for PyGMT v0.4.0) and/or NEP29 adoption (#690). Might depend on whether we want a v0.3.1 release?
Member
There was a problem hiding this comment.
I'm also thinking whether to mention the upcoming drop in support for GMT 6.1.1 (once GMT 6.2.0 is out, something for PyGMT v0.4.0) and/or NEP29 adoption
Don't try to predict the future. 😄
Member
There was a problem hiding this comment.
Ok, will surprise our users then 😸
weiji14 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
weiji14 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
weiji14 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
weiji14 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
weiji14 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
weiji14 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
weiji14 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
weiji14 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
seisman marked this conversation as resolved.
Show resolved
Hide resolved
seisman marked this conversation as resolved.
Show resolved
Hide resolved
weiji14 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
weiji14 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
weiji14 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
weiji14 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
willschlitzer marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
willschlitzer marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
weiji14 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
weiji14 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
weiji14 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
weiji14 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
seisman marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
seisman marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
Outdated
Member
There was a problem hiding this comment.
Suggested change
| @liamtoney, @meghanrjones, @michaelgrund, @seisman, @weiji14 and @willschlitzer | |
| People with a "+" by their name contributed a patch for the first time. | |
| * `Dongdong Tian <https://github.com/seisman>`__ | |
| * `Liam Toney <https://github.com/liamtoney>`__ | |
| * `Meghan Jones <https://github.com/meghanrjones>`__ + | |
| * `Michael Grund <https://github.com/michaelgrund>`__ + | |
| * `Wei Ji Leong <https://github.com/weiji14>`__ | |
| * `Will Schlitzer <https://github.com/willschlitzer>`__ + |
Two thoughts here:
- Should we sort alphebetically by name (as above), or by number of commits (old style before).
- Some projects (e.g. geopandas) add a little note with a plus (+) to indicate people's first contribution, should we add it here?
Member
There was a problem hiding this comment.
Two thoughts here:
- Should we sort alphebetically by name (as above), or by number of commits (old style before).
I'm fine with both, but prefer "number of commits".
- Some projects (e.g. geopandas) add a little note with a plus (+) to indicate people's first contribution, should we add it here?
I saw it in many projects, but is there an easy way to know if someone makes his/her first contribution to this release?
Member
There was a problem hiding this comment.
- Some projects (e.g. geopandas) add a little note with a plus (+) to indicate people's first contribution, should we add it here?
I saw it in many projects, but is there an easy way to know if someone makes his/her first contribution to this release?
Other than remembering people, there's probably a complicated git command that could do it. Happy to leave it without the plus.
I'm fine with both, but prefer "number of commits".
I thought your name would be on top either way, but git shortlog HEAD...v0.2.1 -sne gives:
58 Will Schlitzer <schlitzer90@gmail.com>
54 Dongdong Tian <seisman.info@gmail.com>
9 Wei Ji <23487320+weiji14@users.noreply.github.com>
7 Michael Grund <michael_grund@gmx.de>
6 dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
3 Liam Toney <38269494+liamtoney@users.noreply.github.com>
3 Meghan Jones <meghanj@hawaii.edu>
3 Wei Ji <weiji.leong@vuw.ac.nz>
and so the order would be:
Suggested change
| @liamtoney, @meghanrjones, @michaelgrund, @seisman, @weiji14 and @willschlitzer | |
| * `Will Schlitzer <https://github.com/willschlitzer>`__ | |
| * `Dongdong Tian <https://github.com/seisman>`__ | |
| * `Wei Ji Leong <https://github.com/weiji14>`__ | |
| * `Michael Grund <https://github.com/michaelgrund>`__ | |
| * `Liam Toney <https://github.com/liamtoney>`__ | |
| * `Meghan Jones <https://github.com/meghanrjones>`__ |
Member
There was a problem hiding this comment.
Alright, I'll commit the change, but we should document this (order by number of commits) for when we deal with #885.
Member
There was a problem hiding this comment.
Running git shortlog HEAD...v0.2.1 -sne on the master branch gives me:
54 Dongdong Tian <seisman.info@gmail.com>
54 Will Schlitzer <schlitzer90@gmail.com>
9 Wei Ji <23487320+weiji14@users.noreply.github.com>
7 Michael Grund <michael_grund@gmx.de>
6 dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
3 Liam Toney <38269494+liamtoney@users.noreply.github.com>
3 Meghan Jones <meghanj@hawaii.edu>
Not trying to be listed at the top, just curious why our results are different 😂
Member
There was a problem hiding this comment.
Hmm, I was probably on a different branch (which explains why it had my unversity vuw.ac.nz email). I think you'll get bumped down after @willschlitzer merges this PR though 🤣
Contributor
Author
There was a problem hiding this comment.
Dare I suggest that as a GMT developer and long-time PyGMT maintainer, I think @seisman has definitely earned the first spot!
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.