Hi, Thanks for taking care of this. Performed the followings:
[X] Download links are valid. [X] Checksums and signatures. [X] LICENSE/NOTICE files exist [X] No unexpected binary files [X] All source files have ASF headers [X] Can compile from source [X] Can verify the binary build Note, on the verify binary build I followed the documented process[1]. I’m noticing a bunch of warnings similar to the below: [info] # `pekko-management_2.12-HEAD+20240614-1150.buildinfo`: NOT OK [info] - pekko-management_2.12-HEAD+20240614-1150.jar: Missing in theirs but present in ours [info] - pekko-management_2.12-HEAD+20240614-1150.pom: Missing in theirs but present in ours But I think it is expected. I’m not spotting any mismatch with the content of the files. +1 from me. Thanks in advance. Samuele [1] https://github.com/apache/pekko-site/wiki/Pekko-Release-Process#verifying-the-binary-build > On 14 Jun 2024, at 10:19, laglangyue <jiafu.t...@qq.com.INVALID> wrote: > > +1, on jdk11, m2 > [x] Can compile from source > > > > > ------------------ Original ------------------ > From: > "dev" > > <fannin...@apache.org>; > Date: Fri, Jun 14, 2024 05:57 AM > To: "dev"<dev@pekko.apache.org>; > > Subject: [VOTE] Release Apache Pekko Management 1.1.0-M1-RC1 > > > > Hello Pekko Community, > > This is a call for a vote to release Apache Pekko Management > version 1.1.0-M1-RC1. > > The discussion thread: > > https://lists.apache.org/thread/4nxz67wz9cvn00hrth4zdqcd9gjlsbry > > The release candidate: > > https://dist.apache.org/repos/dist/dev/pekko/MANAGEMENT-1.1.0-M1-RC1/ > > This release has been signed with a PGP key available here: > > https://downloads.apache.org/pekko/KEYS > > Release Notes: > > https://github.com/apache/pekko-management/pull/256/files > > Git tag for the release: > > https://github.com/apache/pekko-management/tree/v1.1.0-M1-RC1 > Git commit ID: fc732afa1b6e11d2d9d7f56fabaad4fd9219c9f2 > > Please download, verify, and test. > > I have also staged jars in the Apache Nexus Repository. These were built > with the same code as appears in this Source Release Candidate. > I 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/ > > For sbt 1.9.4 or greater you can add this resolver > > resolvers += Resolver.ApacheMavenStagingRepo > > Otherwise for older versions of sbt > > 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 PMC 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 for at least 72hrs. > > [ ] +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 > [ ] Can verify the binary build > > To compile from the source, please refer to: > > https://github.com/apache/pekko-management?tab=readme-ov-file#building-from-source > > To verify the binary build, please refer to: > > https://github.com/apache/pekko-site/wiki/Pekko-Release-Process#verifying-the-binary-build > > Some notes about verifying downloads can be found at: > > https://pekko.apache.org/download.html#verifying-downloads > > Here is my +1 (binding). > > Thanks, > PJ Fanning (Apache Pekko PMC member) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org > For additional commands, e-mail: dev-h...@pekko.apache.org
