[x] Backport PRs that have been merged to main to the maintenance branch. Use the "need backport ..." tag if there is one (but don't rely 100% on it)
[x] Verify that no other open issue needs to be addressed before the release.
[x] Test against other ETS packages and other ETS-using projects
[x] Check MANIFEST, requirements, changelog are still up to date.
[x] Test building the documentation
Release
[x] Create branch release/<release version number> from maint/<release version number> branch.
[x] Set release to <release version number>, and set IS_RELEASED is true; commit
[x] Install from source distribution and run tests again
[x] Open a PR against maint/<release version number> with this being the last commit so that CI is built on the release commit
[x] Once CI is done building merge PR
[x] Bump the micro version number i.e. <release version number + 0.0.1> and set IS_RELEASED to false; commit.
[x] Open and then merge a separate PR against maint/<release version number>
[x] From the commit at which IS_RELEASED is true and version is <release version number>, tag (annotated!) git tag -a -m "Release <release version number>" <release version number>
[x] Push the tag git push origin <release version number>
[x] Make PR targeting gh-pages branch: Generate documentation and copy the content to the branch. Verify that the resulting index.html looks good.
[x] Upload to PyPI
[x] Test the PyPI package
Post-release
[x] Package update for enthought/free repository (for EDM)
[x] Backport release note and change log to main, and possibly maint/<release version number> branch.
Target date: 2022-02-24
Release by 2022-02-24
Release blockers
Pre-release
main
to the maintenance branch. Use the "need backport ..." tag if there is one (but don't rely 100% on it)Release
release/<release version number>
frommaint/<release version number>
branch.<release version number>
, and setIS_RELEASED
is true; commitmaint/<release version number>
with this being the last commit so that CI is built on the release commit<release version number + 0.0.1>
and setIS_RELEASED
to false; commit.maint/<release version number>
IS_RELEASED
is true and version is<release version number>
, tag (annotated!)git tag -a -m "Release <release version number>" <release version number>
git push origin <release version number>
gh-pages
branch: Generate documentation and copy the content to the branch. Verify that the resulting index.html looks good.Post-release
enthought/free
repository (for EDM)main
, and possiblymaint/<release version number>
branch.