Add a template for GMT release checklist #893
Conversation
seisman
changed the title
|
Feel free to add more to the checklist! |
There was a problem hiding this comment.
Can add @remkos to the fink package update. We need to find someone to do macports as Florian is probably no longer available.
|
Do we tag after we build the tarballs? With svn we always made the 5.4.x tag and committed, then made the tarball etc so it would have the right settings. |
|
I don't think tagging or not makes any differences in git. A tag is just a pointer to a specific commit hash. In the checklist, I put tagging after making tarballs, because sometimes our tarballs/installers may not work as expected (e.g. #909). If we tag and push it to GitHub, then realize that our tarballs don't work well, we have to make a new tag (i.e. increasing GMT version number). |
|
Need updates after we finish #962. |
|
The only way the order would make a difference is if GMT used the git tag for something. But since the version number is set by cmake then it shouldn't matter. |
seisman
changed the title
|
I updated the release checklist based on our release experience with 6.0.0rc1. This PR is ready for review. |
…ppingTools#893) Bumps [conda-incubator/setup-miniconda](https://github.com/conda-incubator/setup-miniconda) from v2.0.0 to v2.0.1. - [Release notes](https://github.com/conda-incubator/setup-miniconda/releases) - [Changelog](https://github.com/conda-incubator/setup-miniconda/blob/master/CHANGELOG.md) - [Commits](conda-incubator/setup-miniconda@v2.0.0...73b9a80) Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Dongdong Tian <[email protected]>
Created an issue template for GMT release checklist. For each upcoming release, we can open an issue using this template, and tick them off one by one.