You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm thinking of a pydicom v2.4 release as the last one before we put together the Roadmap (see #1759) and start preparations towards Pydicom 3.0 (#1232). I believe this matches with previous discussions we have had.
In addition to the usual checklist below, I think it is time to make the jump to the pyproject.toml based packaging. This was discussed somewhat in #1593, perhaps elsewhere. I've made a start on it, and can do a PR for that. It could be delayed until v3.0, but that might take a while, and it would be nice to handle any packaging issues before the major release.
I'm thinking of a pydicom v2.4 release as the last one before we put together the Roadmap (see #1759) and start preparations towards Pydicom 3.0 (#1232). I believe this matches with previous discussions we have had.
In addition to the usual checklist below, I think it is time to make the jump to the
pyproject.toml
based packaging. This was discussed somewhat in #1593, perhaps elsewhere. I've made a start on it, and can do a PR for that. It could be delayed until v3.0, but that might take a while, and it would be nice to handle any packaging issues before the major release.Release check list (more information)
__dicom_version__
inpydicom/_version.py
- Dicom2023b #1803pydicom/_version.py
to releaseand update the README.md in the release branch
pydicom/_version.py
in master to next development version (major.minor.0.dev0),and update the DOI in the README.md
The text was updated successfully, but these errors were encountered: