You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Priority PRs/issues to complete prior to release**
15
+
-[ ] Wrap X ()
16
+
-[ ] Wrap Y ()
12
17
13
18
**Before release**:
14
19
-[ ] Reserve a DOI on [Zenodo](https://zenodo.org) by clicking on "New Version"
15
-
-[ ] Update Changelog
16
-
-[ ] Add a new entry in `doc/_static/version_switch.js` for documentation switcher
17
-
-[ ] Update citation information https://github.com/GenericMappingTools/pygmt#citing-pygmt
20
+
-[ ] Finish up 'Changelog entry for v0.x.x' Pull Request:
21
+
-[ ] Add a new entry in `doc/_static/version_switch.js` for documentation switcher
22
+
-[ ] Update citation information https://github.com/GenericMappingTools/pygmt#citing-pygmt
23
+
-[ ] Add the documentation link https://github.com/GenericMappingTools/pygmt#documentation-for-other-versions
24
+
-[ ] Add compatibility information https://github.com/GenericMappingTools/pygmt#compatibility-with-python-and-gmt-versions
25
+
-[ ] Copy draft changelog from Release Drafter and edit it to look nice
18
26
19
27
**Release**:
20
-
-[ ] Go to [GitHub Release](https://github.com/GenericMappingTools/pygmt/releases) and make a release, this will automatically create a tag too
21
-
-[ ] Manually upload the pygmt-vX.Y.Z.zip file to https://zenodo.org/deposit, make sure you file it under the correct reserved DOI
28
+
-[ ] At the [PyGMT release page on GitHub](https://github.com/GenericMappingTools/pygmt/releases):
29
+
-[ ] Edit the draft release notes with the finalized changelog
30
+
-[ ] Set the tag version and release title to vX.Y.Z
31
+
-[ ] Make a release by clicking the 'Publish Release' button, this will automatically create a tag too
32
+
-[ ] Manually upload the pygmt-vX.Y.Z.zip file to https://zenodo.org/deposit, ensure that it is filed under the correct reserved DOI
22
33
23
34
**After release**:
24
35
-[ ] Update conda-forge [pygmt-feedstock](https://github.com/conda-forge/pygmt-feedstock)[Usually done automatically by conda-forge's bot]
Copy file name to clipboardExpand all lines: AUTHORS.md
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,7 @@ The following people have contributed code and/or documentation to the project
9
9
(alphabetical by name) and are considered to be "PyGMT Developers":
10
10
11
11
*[Dongdong Tian](https://seisman.info/) | [0000-0001-7967-1197](https://orcid.org/0000-0001-7967-1197) | Michigan State University
12
+
*[Jiayuan Yao](https://github.com/core-man) | [0000-0001-7036-4238](https://orcid.org/0000-0001-7036-4238) | Nanyang Technological University
12
13
*[Leonardo Uieda](http://www.leouieda.com/) | [0000-0001-6123-9515](https://orcid.org/0000-0001-6123-9515) | University of Liverpool
13
14
*[Liam Toney](https://liam.earth/) | [0000-0003-0167-9433](https://orcid.org/0000-0003-0167-9433) | University of Alaska Fairbanks
14
15
*[Malte Ziebarth](https://github.com/mjziebarth) | [0000-0002-5190-4478](https://orcid.org/0000-0002-5190-4478) | GFZ German Research Centre for Geosciences
Copy file name to clipboardExpand all lines: MAINTENANCE.md
+60-41Lines changed: 60 additions & 41 deletions
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,13 @@ making releases, creating packages, etc.
6
6
If you want to make a contribution to the project, see the
7
7
[Contributing Guide](CONTRIBUTING.md) instead.
8
8
9
+
## Onboarding Access Checklist
10
+
11
+
-[ ] Added to [python-maintainers](https://github.com/orgs/GenericMappingTools/teams/python-maintainers) team in the [GenericMappingTools](https://github.com/orgs/GenericMappingTools/teams/) organization on GitHub (gives 'maintain' permissions)
12
+
-[ ] Added as moderator on [GMT forum](https://forum.generic-mapping-tools.org) (to see mod-only discussions)
13
+
-[ ] Added as member on the [PyGMT devs Slack channel](https://pygmtdevs.slack.com) (for casual conversations)
14
+
-[ ] Added as maintainer on [PyPI](https://pypi.org/project/pygmt/) and [Test PyPI](https://test.pypi.org/project/pygmt)[optional]
15
+
-[ ] Added as member on [HackMD](https://hackmd.io/@pygmt)[optional]
9
16
10
17
## Branches
11
18
@@ -47,43 +54,58 @@ conda and the `Makefile` to run the tests and checks.
47
54
48
55
### GitHub Actions
49
56
50
-
There are 5 configuration files located in `.github/workflows`:
57
+
There are 8 configuration files located in `.github/workflows`:
51
58
52
59
1.`style_checks.yaml` (Code lint and style checks)
53
60
54
-
This is ran on every commit to the *master* and Pull Request branches.
55
-
It is also scheduled to run daily on the *master* branch.
61
+
This is run on every commit to the *master* and Pull Request branches.
62
+
It is also scheduled to run daily on the *master* branch.
56
63
57
64
2.`ci_tests.yaml` (Tests on Linux/macOS/Windows)
58
65
59
-
This is ran on every commit to the *master* and Pull Request branches.
60
-
It is also scheduled to run daily on the *master* branch.
61
-
In draft Pull Requests, only one job (Ubuntu + Python latest)
62
-
is triggered to save on Continuous Integration resources.
66
+
This is run on every commit to the *master* and Pull Request branches.
67
+
It is also scheduled to run daily on the *master* branch.
68
+
In draft Pull Requests, only one job (Ubuntu + Python latest)
69
+
is triggered to save on Continuous Integration resources.
63
70
64
-
On the *master* branch, the workflow also handles the documentation deployment:
71
+
On the *master* branch, the workflow also handles the documentation
72
+
deployment:
65
73
66
-
* Updating the development documentation by pushing the built HTML pages from the
67
-
*master* branch onto the `dev` folder of the *gh-pages* branch.
68
-
* Updated the `latest` documentation link to the new release.
74
+
* Updating the development documentation by pushing the built HTML pages
75
+
from the *master* branch onto the `dev` folder of the *gh-pages* branch.
76
+
* Updating the `latest` documentation link to the new release.
69
77
70
78
3.`ci_tests_dev.yaml` (GMT Dev Tests on Linux/macOS/Windows).
71
79
72
-
This is triggered when a PR is marked as "ready for review", or using the slash
73
-
command `/test-gmt-dev`. It is also scheduled to run daily on the *master* branch.
80
+
This is triggered when a PR is marked as "ready for review", or using the
81
+
slash command `/test-gmt-dev`. It is also scheduled to run daily on the
82
+
*master* branch.
74
83
75
84
4.`cache_data.yaml` (Caches GMT remote data files needed for GitHub Actions CI)
76
85
77
-
This is scheduled to run every Sunday at 12 noon.
78
-
If new remote files are needed urgently, maintainers can manually uncomment
79
-
the 'pull_request:' line in that `cache_data.yaml` file to refresh the cache.
86
+
This is scheduled to run every Sunday at 12:00 (UTC).
87
+
If new remote files are needed urgently, maintainers can manually uncomment
88
+
the 'pull_request:' line in that `cache_data.yaml` file to refresh the cache.
80
89
81
90
5.`publish-to-pypi.yml` (Publish wheels to PyPI and TestPyPI)
82
91
83
-
This workflow is ran to publish wheels to PyPI and TestPyPI (for testing only).
84
-
Archives will be pushed to TestPyPI on every commit to the *master* branch and
85
-
tagged releases, and to PyPI for tagged releases only.
92
+
This workflow is run to publish wheels to PyPI and TestPyPI (for testing only).
93
+
Archives will be pushed to TestPyPI on every commit to the *master* branch
94
+
and tagged releases, and to PyPI for tagged releases only.
95
+
96
+
6.`release-drafter.yml` (Drafts the next release notes)
97
+
98
+
This workflow is run to update the next releases notes as pull requests are
99
+
merged into master.
100
+
101
+
7.`check-links.yml` (Check links in the repository and website)
102
+
103
+
This workflow is run weekly to check all external links in plaintext and
104
+
HTML files. It will create an issue if broken links are found.
86
105
106
+
8.`format-command.yml` (Format the codes using slash command)
107
+
108
+
This workflow is triggered in a PR if the slash command `/format` is used.
0 commit comments