7.4.2 Release Checklist

Target date:

Release Candidate by YYYY-MM-DD

Release by YYYY-MM-DD

Release blockers

None

[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

[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] merge the PR when it is approved
[x] Create a post-release PR branch from maint/<release version number> branch.
- [x] Bump the micro version number i.e. <release version number + 0.0.1> and set IS_RELEASED to false; commit.
- [x] Open a separate PR against maint/<release version number>
- [x] merge the PR when it is approved
[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] Update GitHub Release pages https://github.com/enthought/pyface/releases A Github workflow should automatically publish the release to PyPI.
[x] Test the PyPI package
[x] Backport release notes and change log to the main branch.