New release?

[Neustradamus]

Dear @lz4 team, @Cyan4973,

I wish you a Happy New Year 2024.

It is possible to create a new release build?

The latest is 1.9.4 (2022-08-16):

• https://github.com/lz4/lz4/releases
• https://github.com/lz4/lz4/tags

Thanks in advance.

[Cyan4973]

There will be a release this year.
There is just no set date yet.

[es20490446e]

I just liked to say I'm finding your compression algorithms VERY useful. I'm using them at everything you can imagine.

Thanks 😉

[HTHou]

Also looking forward a new release of lz4-java. :-)

[t-mat]

I made a new milestone v1.9.5 and add some issues.

https://github.com/lz4/lz4/issues?q=is%3Aissue+milestone%3Av1.9.5

If you notice/think any other issues which should be addressed as a part of v1.9.5, please tell us about them.

[Neustradamus]

@t-mat: Thanks, I hope that issues will be solved soon...

[JakeMerdichAMD]

@t-mat: would #791 (stabilize dictionary training api) be an appropriate addition for v1.9.5? The last relevant comment (in 2019!) said The dictionary API was still too young to be added to "stable" for v1.9.0, but it's definitely an item on the list for next important update, be it v1.10.0 or v2.0.0 (not decided yet).. This can have an incredible benefit for certain use cases, and equivalent features in zstd are looking to make its way into an IETF spec.

We've been using it in some C/C++ libs with static linking, but many lz4 bindings don't want to add the feature until it's stable-- which is fair. This makes it a bit of a pain for interoperability (or ad-hoc python scripts).

[Cyan4973]

This would push the release number to v1.10, instead of v1.9.5,
but that seems like a reasonable request.

The main reason this API is not categorized "stable" yet is that I don't know about much usage of this API outside of our own production environment, which means it's lacking some kind of "real production feedback".

Of course, it's also a chicken/egg problem, since many potential users do not employ this API because it's not stable. But then, if it's stable, it's not supposed to change anymore, which limits the kind of adaptation that can be done.

Anyway, I could consider this item for next release nonetheless.

[es20490446e]

Don't expect software to be completely stable. It shall have a stable base, with some beta on it. A controlled amount.

As long as this beta is well tested to work for you, it's good enough.

Otherwise you will find yourself in chicken/egg.

[teo-tsirpanis]

I would appreciate a release with #1372 and #1413. There is a divergence between upstream lz4 and its vcpkg port with regards to the exported CMake packages and targets and the casing of their names, and a release with these PRs would help towards closing the gap and unifying the ecosystem.