Release 1.2.0

[eustas]

This is what needs to be finished for for release:

• renovate PY binging; support multi-phase module initialization
• drop "finalize" in Java
• address Use-after-free in BrotliEncoderCompressStream when prepared dictionary retains pointer to caller buffer #1331
• roll out rc1

Extra release steps:

• release Java package
• release wheels / PyPI
• consider packaging JS version

Feel free to write in comments what you think is missing in that list.

[celestinoxp]

Point 1 - I think this will take a while... can you give an estimate?
Point 2 - It's just a question, but in an idea tone: Does it make sense to release a new version now while version 1.2 isn't finished and released...? For example, 1.1.1... maybe this would help to get more feedback in preparation for version 1.2.

Any ideias @osokin @rbri @AndreasA @eustas ?

[eustas]

Lets try to release before October. As for intermediate release, that would be RC. I will try to roll that out till next Wednesday.

[eustas]

Sorry, did not cut rc1 today. Hopefully, tomorrow.

[osokin]

Sorry, did not cut rc1 today. Hopefully, tomorrow.

Still no rc1.

[eustas]

True. Waiting for review for multi-phase-initialization #1334 (first checkbox). Sorry.

[eustas]

There are more things I'd like to see in release, but we are ready to cut rc1 🍰

[eustas]

rc1 is cut!

[alexprengere]

Now that Python3.14 is officially released, would it be possible to generate the corresponding wheels?

[eustas]

Sure, nice timing. @anthrotype what do we need to do for that?