Hi all, this release was the first done by the scripts in “tools”. With this I am trying to make releasing easier and to make it harder for RMs to miss things. However, the probably major difference is that the final release:perform-release step is executed in a Docker-container, which should make the build fully reproducible. I am planning on building some additional tooling, that allows people to validate releases additionally by downloading the content of the staging repo and doing binary comparisons with what’s built from the local sources. Also, could people download our releases and run the script and compare that what they are using in the company is binary identical what they would build locally.
I think that’s going to be pretty cool. Happy voting … I would love to release the release on Tuesday, so please do me a favor and plan in some time for voting. Ideally as soon as possible, so we could possibly have a bit more time, in case an RC2 is needed, as I would love to have the release out the door before Building IoT Conference next week and to have our website in-line with the currently latest released version as soon as possible. Chris Von: Christofer Dutz <christofer.d...@c-ware.de> Datum: Freitag, 16. Februar 2024 um 13:59 An: dev@plc4x.apache.org <dev@plc4x.apache.org> Betreff: [DISCUSS] Apache PLC4X 0.12.0 RC1 This is the discussion thread for the corresponding VOTE thread. Please keep discussions in this thread to simplify the counting of votes. If you have to vote -1 please mention a brief description on why and then take the details to this thread.
