Update release process in template post v0.3.0 #907
Merged
Conversation
This file contains 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
Documenting some of the lessons learned from Release v0.3.0 so that the next one will be smoother.
weiji14
added
documentation
seisman
reviewed
Feb 17, 2021
9 tasks
seisman
reviewed
Feb 23, 2021
Co-Authored-By: Dongdong Tian <seisman.info@gmail.com>
Bump up version number when a 'feature' PR is merged. Otherwise only increment to a patch version as per semver. See docs at https://github.com/release-drafter/release-drafter/tree/v5.14.0#version-resolver
seisman
approved these changes
Mar 1, 2021
sixy6e
pushed a commit
to sixy6e/pygmt
that referenced
this pull request
Dec 21, 2022
Documenting some of the lessons learned from Release v0.3.0 so that the next one will be smoother. The Release Drafter bot will also automatically increment to the next minor version (instead of a patch version) when a PR tagged 'feature' is merged into the master branch. Co-Authored-By: Dongdong Tian <seisman.info@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of proposed changes
Documenting some of the lessons learned from Release v0.3.0 (#845, #887) so that the next one will be smoother. The Release Drafter bot will also automatically increment to the next minor version (instead of a patch version) when a PR tagged 'feature' is merged into the master branch.
Addresses the documentation part of #885 and also closes #945.
Reminders
make formatandmake checkto make sure the code follows the style guide.doc/api/index.rst.Slash Commands
You can write slash commands (
/command) in the first line of a comment to performspecific operations. Supported slash commands are:
/format: automatically format and lint the code/test-gmt-dev: run full tests on the latest GMT development version