On Thu, Jun 29, 2023 at 10:24 AM Matthew Benedict de Detrich <matthew.dedetr...@aiven.io.invalid> wrote: > This is why we came up with the "Leave the 1.0.0 artifacts up for 3 > business days so that the community can verify that they match the latest > successfully voted RC artifact" rule in > https://github.com/apache/incubator-pekko-site/wiki/Pekko-Release-Process#build-the-release > as a compromise between how other major TLP projects work and not needing > what is seen as an unnuccessary vote.
Not sure, if that's really a compromise, as the changed binary artifacts can have different semantics with the changed versions numbers. So, while we could avoid reevaluating the source release which should (enforced to) be identical between RC and final release, the binaries need to be reevaluated rather more strictly than in other projects that 1) don't change semantics with version numbers and 2) don't need to be rebuilt for the final release. In particular, there's logic in pekko modules to restrict which module versions are allowed to be combined at runtime. Currently, the rule is a simple equality check that validates that all pekko core modules are at the same version at runtime, so the risk is currently low to get it wrong. The other risk regarding binaries is the general risk that the required manual release process can go differently (wrong) between RC and final release. Not sure if we can or should skip the vote, but we should definitely not skip the evaluation of the final binaries. Johannes --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org For additional commands, e-mail: dev-h...@pekko.apache.org
