-
Notifications
You must be signed in to change notification settings - Fork 68
Description
pims v0.4.1 was released in 2017. Support for some formats, especially still images, continues to work great in that release, but there have been many improvements, bug fixes, and high-profile API changes since then, most notably a fix for PyAV support.
I'm creating this thread to help us (maintainers and contributors) decide what minimally needs to be done, and what decisions must be made before we can proceed with a release. Actually doing a release and documenting the procedure again will make it easier to do minor releases as more work is done.
Here's what I see as the key steps:
- Rebase and merge ENH Add crop pipeline #247 since it's a nice enhancement with few or no side effects.
- Even though Speed up random access time of PyAVReaderIndexed. #340 is relatively new, we should try to merge it because it's such a huge performance increase.
- Fix the problem with bioformats in Jpype1 0.7 breaks bioformat integration #330 , at least by requiring Jpype ≤ 0.6.3.
- Get more help with bioformats! Bump loci_tools to 6.4.0 #301 may be obsolete, and I know almost nothing about bioformats. Update Bioformats #318 is related and looks important. If anyone (maintainer, or contributor) knows whether this is still an important fix, it would be great to find out!
- Review and merge a PR I'm preparing to update the release notes.
- Publish the release and copy the relevant portions of the release instructions in the trackpy wiki.
There are other PRs that are worth attention but are probably not ready for a timely release:
- Better support for numpy interface. #254 looks like it's still cooking, and @danielballan may be evaluating other approaches. He can correct me if I'm wrong.
- Base ImageIOReader on FramesSequenceND #320 seems worthwhile but it's unclear to me how big an API change this is; it at least needs to be documented. So I'm inclined to leave it until v0.6 unless @rbnvrw wants to finish it soon.
- WIP: Ensure
openhandleslists correctly #316 is likewise worthwhile but needs some work. I suggest we leave it out.
Note that I am not (yet) volunteering to do this release! I just want us to start by getting organized. Please comment on this plan — what am I missing?