New Release?

[eddybl]

Hey,

as there was a lot of progress on this package, maybe we should go for a new release? the last one was from 2020 and even though there are active open PRs, maybe it is still worthwhile to do a new release?

[tynanford]

Yes we should. I am thinking we could wait until the 3 active PRs are completed but that isn't a super strong preference. The PRs are almost ready so it shouldn't be too long.

We could also create a retroactive release, I was thinking tagging here: https://github.com/epics-modules/pyDevSup/tree/1e933f312fa24e52a104fe1ecab4075de2fe86d5 . That would include the updates for numpy v2 and newer python versions (and dropping python2) and give us a release before the recent changes. What do you all think?

Also tagging @pheest @zhangt58

[tynanford]

I propose we do two releases:

2.0: https://github.com/epics-modules/pyDevSup/tree/1e933f312fa24e52a104fe1ecab4075de2fe86d5 (drops python 2, sets minimum at 3.6, adds numpy v2 support)
2.1: New release once remaining 3 PRs are merged. This will include windows support, amsg updates, long string/int64/calcout, and cleanup

[eddybl]

sounds good to me