Release v1.1

[eustas]

This is an umbrella / checklist issue.

• mark release candidate
• actually release
• release Java package | see Java builds missing from Maven for releases after 0.1.2 #715

[GitMensch]

@eustas wrote on January 3rd

Getting closer to it. Now working on the issues list and then we will have a release =)

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]

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]

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]

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]

Congrats for the 1.1 release!

Will the 10 open issues in the 1.1 milestone be moved to another milestone?

[eustas]

Correct

[eustas]

Done. We hope to make next release rather soon, lets say after a month or two.

[diizzyy]

@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]

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]

Thanks, tracked as #1076

[bric3]

Hello, any updates on getting the new Java artifacts on maven central ?

[slandelle]

@bric3 Are you aware of Brotli4j?

[bric3]

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]

Releasing Java moved to 1.1.1 (issue was fixed in wrapper code)