> The nexus artifacts that we're currently voting on are 1.0.0-RC3, but I'm more familiar with voting for an actual release like 1.0.0 (or often 1.0.0-incubating). Recompiling and redeploying new binary artifacts after the release vote seems strange to me.
This is intentional, because Pekko is a library this means a significant part of testing would involve updating/adding Pekko as a dependency to sbt/gradle/maven projects and since non SNAPSHOT artifacts are considered immutable, a lot of JVM based build tools will cache the artifacts indefinitely which causes issues if you have multiple RCs per release. Although there are ways around this, the existing Akka/Pekko user/dev base are not used to this (the Scala OS, including Akka ecosystem predominantly uses RC suffixes). On Thu, 29 June 2023, 21:10 Ryan Skraba, <[email protected]> wrote: > +1 (binding) > > I've validated this release candidate: 1.0.0-RC3 at SVN revision r62739 > * The SHA256 and SHA512 hashes are OK. > * The source files are signed correctly. > * The signature 6BA4DA8B1C88A49428A29C3D0C69C1EF41181E13 is found in the > KEYS file, and on at least one keyserver. > * The incubating-pekko-src-1.0.0-20230629.tgz and .zip have consistent > contents. > * The source files are consistent with the Github tag v1.0.0-RC3, which > corresponds to commit > > https://github.com/apache/incubator-pekko/tree/4ce1095b4b48f5cdd31342ab9f0950bd44a2829a > * Some github only files like .gitignore aren't present, but that's > expected. > * Has a DISCLAIMER, LICENSE and NOTICE files. The LICENSE file starts with > the ASL2 text. > * Does not contain any compiled binaries. > * Has many artifacts staged at > https://repository.apache.org/content/groups/staging/org/apache/pekko/ > > While I didn't download and verify every artifact in the nexus, I did check > the signature on a couple. > > A couple of non-blocking things that we might consider for the next release > cycle! > > * Instead of using yet another filename format. Pekko is the only project > in the Incubator SVN that puts the words "incubating" before the project > name, and "source" before the release number. > > * The nexus artifacts that we're currently voting on are 1.0.0-RC3, but I'm > more familiar with voting for an actual release like 1.0.0 (or often > 1.0.0-incubating). Recompiling and redeploying new binary artifacts after > the release vote seems strange to me. > > * It's probably unnecessary to double up on SHA-512 and SHA-256 signatures, > or to double up the .zip as well as .tgz. > > All my best and thanks for the RC! > > Ryan Skraba > > > On Thu, Jun 29, 2023 at 3:49 PM PJ Fanning <[email protected]> wrote: > > > Hello Pekko Community, > > > > This is a call for a vote to release Apache Pekko(incubating) version > > 1.0.0-RC3. > > > > The discussion thread: > > > > https://lists.apache.org/thread/xd4wp77bdwyll9243mnd9qc6j4d122kr > > > > The release candidate: > > > > https://dist.apache.org/repos/dist/dev/incubator/pekko/1.0.0-RC3/ > > > > This release has been signed with a PGP key available here: > > > > https://dist.apache.org/repos/dist/dev/incubator/pekko/KEYS > > > > Release Notes: > > > > > https://cwiki.apache.org/confluence/display/PEKKO/Pekko+Core+Release+Notes > > > > Git branch for the release: > > > > https://github.com/apache/incubator-pekko/tree/v1.0.0-RC3 > > Git commit ID: 4ce1095b4b48f5cdd31342ab9f0950bd44a2829a > > > > Please download, verify, and test. > > > > We have also staged jars in the Apache Nexus Repository. These were > > built with the same code > > as appears in this Source Release Candidate. We would appreciate if > > users could test with these too. > > If anyone finds any serious problems with these jars, please also > > notify us on this thread. > > > > https://repository.apache.org/content/groups/staging/org/apache/pekko/ > > > > In sbt, you can add this resolver. > > > > resolvers += "Apache Pekko Staging" at > > "https://repository.apache.org/content/groups/staging"; > > > > > > The VOTE will pass if we have more positive votes than negative votes > > and there must be a minimum of 3 approvals from Pekko PPMC members. > > Anyone voting in favour of the release, could you please provide a > > list of the checks you have done? > > The vote will be left open until 23:00 UTC on 4 July 2023. > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > To learn more about Apache Pekko, please see https://pekko.apache.org/ > > > > Checklist for reference: > > > > [ ] Download links are valid. > > [ ] Checksums and signatures. > > [ ] LICENSE/NOTICE files exist > > [ ] No unexpected binary files > > [ ] All source files have ASF headers > > [ ] Can compile from source > > > > To compile from the source, please refer to: > > > > > > > https://github.com/apache/incubator-pekko/blob/main/README.md#building-from-source > > > > Some notes about verifying downloads can be found at: > > > > https://pekko.apache.org/download.html#verifying-downloads > > > > > > Here is my +1. > > > > Thanks, > > > > PJ Fanning (Apache Pekko PPMC member) > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
