Release 0.13.1 checklist
See original GitHub issuePreparing the release
- ~Rerun all notebooks (pay special attention to new features)~
- ~Review documentation, optionally improving the user guide or adding new notebooks showcasing new functionality~
- Write the changelog and list of contributors
- Commits since last release branch https://github.com/poliastro/poliastro/compare/0.13.0...master
- Issues closed in this milestone https://github.com/poliastro/poliastro/issues?q=is%3Aissue+is%3Aclosed+closed%3A>%3D2019-07-21+sort%3Aupdated-asc
- Pull requests merged since last branching https://github.com/poliastro/poliastro/pulls?q=is%3Apr+is%3Amerged+merged%3A>%3D2019-07-21+sort%3Aupdated-asc
- Add 0.13.x branch to CI scripts
Before the beta release
- New branch
- Bump version to 0.13.1b1 in:
README.rst
__init__.py
- Sphinx
conf.py
- AppVeyor CI script
- Check that the release branch will be tested on CI
- Check all the badges in
README
point to the appropriate git branch (replacemaster
by new branchsed -i 's/master/.../g' README.rst
) - Check that docs badges and URLs point to appropriate tag (replace
latest
by new tag, without sed!) - Commit
- Generate sdist and bdist_wheel
-
twine upload dist/* --repository-url https://test.pypi.org/legacy/
- Tag
- Bump master to next development version
Beta release
- Push branch to GitHub and tags
- Check on Test PyPI that the badges will work
- Upload sdist and bdist_wheel to PyPI - this step cannot be undone if the release is removed!
twine upload dist/* --repository-url https://upload.pypi.org/legacy/
- Check Read the Docs (check https://docs.readthedocs.io/en/latest/webhooks.html#github first)
Before final release
- Backport any bugs
- Update release date in changelog
- Bump version to 0.13.1 in:
README.rst
__init__.py
- Sphinx
conf.py
- AppVeyor CI script
- Check that docs badges and URLs point to appropriate tag (replace
v0.13.1b1
byv0.13.1
) - Commit
- Generate sdist and bdist_wheel
-
twine upload dist/* --repository-url https://test.pypi.org/legacy/
- Tag
Final release
- Push tag to GitHub
- Upload sdist and bdist_wheel to PyPI - this step cannot be undone if the release is removed!
twine upload dist/* --repository-url https://upload.pypi.org/legacy/
- Check Read the Docs (check https://docs.readthedocs.io/en/latest/webhooks.html#github first)
- Create GitHub release
- Add Zenodo badge to GitHub release
- Send announcement email
- Cherry pick release date to master
- Close milestone
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
WLED 0.13.1 - Preset Calendars ! - YouTube
Finally we can schedule the our DIY Holiday LEDs to come on during set days of the year!
Read more >Releases · Aircoookie/WLED - GitHub
The complete list of changes is still TBD, but will be available in the changelog ... This version's highlights are (in addition to...
Read more >Publish Operator 0.13.1 (#921) · Issues - GitLab
This issue will serve as a checklist and record of releases for GitLab Operator 0.13.1 . Much of the process is automated by...
Read more >Command: 0.13upgrade | Terraform - HashiCorp Developer
The provider source settings are stored in a required_providers block. This command is available only in Terraform v0.13 releases. For more information, see...
Read more >KBase Workspace Service Manual
Workspace service release notes ... VERSION: 0.13.2 (Released 6/1/2022) · VERSION: 0.13.1 (Released 4/27/2022) · VERSION: 0.13.0 ... Documentation TODO list ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
They are in
master
though, and we will make a release in the0.13.x
branch, so I will backport them.Thanks @olebole!