v2.2 Release

[scaramallion]

Release date is approximately May 2021

Core

• Continue improving typing
• Memory mapping for bulk data elements
• CLI

Documentation

• Pixel data decoding and encoding (native)
• Pixel data encoding (encapsulated)
• Creating conformant SOP instances from scratch
• Add ability to browse docs from previous versions

[scaramallion]

Should we do a release soon? The only real outstanding issues are related to SR (#1388, #1273) and I'm not sure how you want to handle them.

Also, do we want to re-enable typing? I'm sure there'll be issues but it'd be good to get a wider set of eyes on it.

[darcymason]

Yes.

I'd like to do a release candidate, so we can try typing on for that and request feedback.

I do have to try to resolve the asserts issue in #1388 that I promised to look at. Can hopefully look at that in next couple of days.

[diegacu]

Hi!
Quick question. Is there any date planned on when will the 2.2 version be released?
Thanks

[darcymason]

Is there any date planned on when will the 2.2 version be released?

It was intended to be out some time ago; I've been busy with other things. I'll try to get out a release candidate this week, then it can be installed with the --pre option of pip.

[FezVrasta]

Hi, was there any update on a release?

I'd need the fix for this change:

https://github.com/pydicom/pydicom/blob/v2.1.2/pydicom/dataelem.py#L367

https://github.com/pydicom/pydicom/blob/master/pydicom/dataelem.py#L377

[darcymason]

Hi, was there any update on a release?

I'll look into latest problem I noted in #1388 today. If that can't be solved quickly, I think I might release on a commit before that problem. @scaramallion, @mrbean-bremen, any thoughts? Since we (by that I mean "I") am behind on this release, the next release wouldn't be far away anyway, to get back on the 4-month schedule.

[mrbean-bremen]

I don't see anything that hinders a release. If you don't get this SR issue resolved now, that may get into a dot release later (maybe together with the PRs made by @hackermd). Better to get a release out now IMHO.

[hackermd]

@mrbean-bremen Agreed! I think it would be valuable to get v2.2 out first. We can then continue to work on the remaining issues and PRs and hopefully release a new version relatively soon.

[darcymason]

A release candidate (v2.2.0-rc.1) has been published to PyPi. Can be installed with pip install --pre pydicom.

I'll announce it more widely tomorrow and then give it a few days to see if anyone reports problems.

Github now has option to start a discussion automatically with the release, so I did that for this.

[darcymason]

The final 2.2.0 has been created in the 2.2.X branch, published to PyPi, the gh-pages documentation updated, and the DOI updated.

Now will try to rebase back into master to keep the tag in the main branch history.

[darcymason]

Conda-forge PR merged in. Closing this issue now, any issues can go on the regular issue list.