-
Notifications
You must be signed in to change notification settings - Fork 122
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* deprecate filters argument * remove unused version info in setup.py * update gallery for filter deprecation * bump references down one toc level * update release notes * starting to work on a release procedure * better message in makefile * use VENV_DIR everywhere * more notes * finish release procedure * additional note * get pyam version in docs from introspection * try new list * new list again * final release notes
- Loading branch information
Showing
15 changed files
with
101 additions
and
54 deletions.
There are no files selected for viewing
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,42 @@ | ||
|
||
# Steps required for a release | ||
|
||
1. Make a release candidate branch and pull request it into master with the following updates: | ||
1. Deprecate any stated portion of the API (you can find them by searching the code base for "deprecate") | ||
1. Update `RELEASE_NOTES.md` (see the examples of other releases) | ||
- create new section under "# Next Release" with "# Release v<release version>" | ||
- For this new release, add a "Highlights section" with some of the most important updates | ||
- Make a new heading "## Individual Updates" before the PR listing | ||
1. Confirm that the PR passes all tests and checks | ||
1. Tag the release number: `git tag v<release version>`, e.g., `git tag v1.2.0` | ||
- **THIS IS NOT THE TAGGED COMMIT WE WILL DISTRIBUTE, IT IS ONLY FOR TESTING** | ||
- **DO NOT PUSH THIS TAG TO UPSTREAM** | ||
1. Run `make publish-on-testpypi` | ||
- this should "just work" if it does not, fix any issues, retag (`git tag | ||
-d` then `git tag`), and try again | ||
- note, you need an account on https://test.pypi.org | ||
1. Once successful, delete the tag, and merge the candidate PR into master on Github | ||
1. Switch to now updated master branch: `git checkout master` and `git pull upstream master` | ||
1. Tag the release number: `git tag v<release version>`, e.g., `git tag v1.2.0` | ||
- `versioneer` automatically updates the version number based on the tag | ||
- this is now the official tagged commit | ||
1. Push the tag upstream: `git push upstream --tags` | ||
1. Run `make publish-on-pypi` | ||
- note, you need an account on https://pypi.org | ||
- this will make wheels that all us to be installed via `pip install` | ||
1. Update on conda-forge: | ||
- Issue a PR on https://github.com/conda-forge/pyam-feedstock following the | ||
instructions there for how to edit the `recipe/meta.yaml` file | ||
- confirm that any new depedencies are added there | ||
- Note that you can get the correct SHA256 hash from | ||
https://pypi.org/project/pyam-iamc/#files once that step has been | ||
successful | ||
1. Make a new release on Github | ||
- Make sure that you choose the same tag name as was used earlier | ||
- Copy the markdown from `RELEASE_NOTES.md` into the release description box | ||
1. Announce it on our mailing list: https://groups.google.com/forum/#!forum/pyam | ||
- Again, just copy the now rendered HTML from the Github release directly in | ||
the email | ||
1. Confirm that the doc page is updated to the latest release: https://pyam-iamc.readthedocs.io/ | ||
|
||
And that's it! Whew... |
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
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
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
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
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
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
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
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
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
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
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
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