mirror of
https://github.com/google/brotli.git
synced 2026-07-08 17:56:58 +00:00
Release v1.1 #473
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @eustas on GitHub (Aug 3, 2023).
Originally assigned to: @eustas on GitHub.
This is an umbrella / checklist issue.
@GitMensch commented on GitHub (Aug 16, 2023):
@eustas wrote on January 3rd
If there are any show-stoppers found in the issue list then please add them to this list and drop a note once the list is considered to be complete.
Thank you.
@eustas commented on GitHub (Aug 16, 2023):
Most likely we are going to land new features in parts. I.e. "raw dictionaries" first (v1.1) and serialized dictionaries later.
That would require some time for updating API in clean but non-breaking manner.
Thanks for patience.
@GitMensch commented on GitHub (Aug 16, 2023):
The question is: Do we need even more features or can the current version be considered stable -> released, then get more features in future releases - even in the unlikely case that the next release after the "still-to-be-released" one is only 1 to 4 months away.
@eustas commented on GitHub (Aug 16, 2023):
Exactly. The last comment was about cutting off (removing) non-stabilized feature for release (see https://github.com/google/brotli/blob/master/c/include/brotli/shared_dictionary.h#L39)
@GitMensch commented on GitHub (Aug 31, 2023):
Congrats for the 1.1 release!
Will the 10 open issues in the 1.1 milestone be moved to another milestone?
@eustas commented on GitHub (Aug 31, 2023):
Correct
@eustas commented on GitHub (Aug 31, 2023):
Done. We hope to make next release rather soon, lets say after a month or two.
@diizzyy commented on GitHub (Sep 9, 2023):
@eustas
Thanks for your time working on this projects!
Is it possible to generate a static source archive next release due to https://github.blog/2023-02-21-update-on-the-future-stability-of-source-code-archives-and-hashes/ which would help packagers a lot?
@eustas commented on GitHub (Sep 9, 2023):
Sure, will do my best. Ideally you need to make a separate issue for that, so it do not fall of my radar. Thanks.
@diizzyy commented on GitHub (Sep 9, 2023):
Thanks, tracked as https://github.com/google/brotli/issues/1076
@bric3 commented on GitHub (Dec 15, 2023):
Hello, any updates on getting the new Java artifacts on maven central ?
@slandelle commented on GitHub (Dec 15, 2023):
@bric3 Are you aware of Brotli4j?
@bric3 commented on GitHub (Dec 15, 2023):
Hi @slandelle Yes I am. But Brotli 4J is using native libraries, which are not always compatible with the platform. Also, in the past, I remember having some issues integrating it with ktor (kotlin coroutine's based), maybe that has changed.
That said I would prefer to use the JVM based google code if possible.
@eustas commented on GitHub (Jan 11, 2024):
Releasing Java moved to 1.1.1 (issue was fixed in wrapper code)
@GitMensch commented on GitHub (Jun 21, 2024):
@eustas that sounds really nice - can you please create a meta-issue like this one for the next version (and possibly make it sticky so it is easily recognizable)?