Closed sezero closed 1 year ago
No clue currently, but I'll go ahead and pin this issue.
Going down the list of open issues, I think #14, #25, and #26 should definitely be resolved. I'm not familiar enough with libnotify to handle #8, but it doesn't seem unreasonable. #32 (which I just opened) has been annoying for a while but isn't particularly serious.
It looks like there's a commit that labels a "4.2.0" release, but it wasn't tagged or released as a tarball: fa8286eeb1deb4a5679169bdf798039552fe6067 Are there any plans for that?
Still waiting for things to clear up.
What do we definitely need to do before doing a 4.2.0 release?
None of the things I listed are essential for a release, I think this could be done any time.
Tagged and created a 4.2.0 release: https://github.com/libxmp/xmp-cli/releases/tag/xmp-4.2.0
What is needed to make a new 4.2.0 release?