Closed jubalh closed 2 years ago
@jubalh Some of the changes that I have merged to master (for JPEG 2000 conformance) since the last JasPer release will potentially break ABI compatibility. So I think that we may need a new shared library version. I still have a few more changes to push. So, I think that we should holdoff on a new release for now.
@jubalh Just to add to my previous comment: I am sorry but I had intended to finish my JPEG-2000 conformance changes last month, but I have just been too busy lately with work to finish this.
I still have a few more changes to push. So, I think that we should holdoff on a new release for now.
Alright I see!
I am sorry but I had intended to finish my JPEG-2000 conformance changes last month, but I have just been too busy lately with work to finish this.
No problem!
Maybe you can ping me here once that's done (even if it is only in some weeks or months) then I'll update this PR with the new changes :)
Why don't you update the NEWS file but leave the version and date as XXXXXXX. I can then merge this now. Then, I can later replace the X's when I do the release. This way I will pickup your additions to the NEWS file.
Good idea. Should be done now.
Due to CVE-2022-2963 I propose to release 3.0.7.
@mdadams I'm not sure whether you are working on more things for the next release. Please comment/merge at your discretion.
Questions: