Repository navigation
About ITK 5.4.8 #6920
Description
Release checklist and status:
- Check dashboard and CI
- Tag the ITK repository
- Bump ITK's version
- Update
releasebranches - Bump the ITKPythonPackage version
- Generate InsightToolkit and InsightData tarballs
- Archive testing data
- Generate Python packages and ITKPythonBuilds
- Update conda-forge/libitk-feedstock
- Update conda-forge/itk-feedstock
- Update ITKSoftwareGuide
- Upload Python packages to PyPI
- Update and test versions in ITKRemoteModuleBuildTestPackageAction
- Tarballs archived on ITKReleases NumFOCUS GDrive
- Write release notes
- Publish GitHub Release
- Update downloads page
- Post on Discourse
- Post on Open Collective
- Post on Image.sc
- Post on Wordpress for itk.org entry
Activity
blowekamp commentedon Oct 14, 2026
I have tested the current ITK release-5.4 branch of ITK against SimpleITK; everything passes OK.
blowekamp commentedon Oct 27, 2026
@thewtex @dzenanz Are we able to move forward with this patch release tag?
dzenanz commentedon Oct 27, 2026
Maybe one more PR, and it is ready for tagging. The effort is in going through the release checklist. Any one of us should be able to do it? Some steps require permissions, e.g. Matt can push wheels to PyPI, but not me and you @blowekamp. Similarly, you and Matt have write permissions to conda-forge, and I don't.
dzenanz commentedon Oct 28, 2026
@hjmjohnson I would like to have a version of Cuberille with the fixes available via PyPI release, sooner rather than later. Does it make sense to backport fixes from #6302 into the remote, then reference that from ITK 5.4.8? Next 6.0 release (beta 3?) seems to require more work to materialize.
thewtex commentedon Oct 29, 2026
The release has been tagged, thank you for your patience.
Absolutely not. In my experience, the effort is not merely a robotic walkthrough of this checklist.
dzenanz commentedon Oct 29, 2026
The effort is in making sure everything is working properly, so we can do every step of the checklist. Is this better phrasing?
thewtex commentedon Oct 29, 2026
No.