I'm not against doing a Pekko 1.1.6 release. We already have a milestone for that. We can backport bug fixes to Pekko 1.1.x branch and do a release for 1.1.6.
On Wed, 27 Aug 2025 at 11:24, kerr <hepin1...@gmail.com> wrote: > [image: image.png] > > Because there is a bug in the harmless shutdown, you fixed that , and we > need this, and which is not being backport to pekko 1.1.x > > https://github.com/apache/pekko/pull/1555 > > 何品 > > > PJ Fanning <fannin...@gmail.com> 于2025年8月27日周三 18:17写道： > >> I don't think the Pekko team should be making big refactors like this. >> Why don't you stick with Pekko 1.1 if you are not ready to upgrade Netty? >> All in all, this is better discussed on the GitHub issue. >> >> On Wed, 27 Aug 2025 at 11:07, kerr <hepin1...@gmail.com> wrote: >> > >> > I encountered a problem at work, >> https://github.com/apache/pekko/issues/2099 >> > >> > A workmate is bumping their system from Akka to Pekko 1.2-M2, but the >> other >> > dependencies is still using Netty 4.1.2, so after the migration, she >> has to >> > exclude the Netty 4.2 dependencies. >> > >> > Our RPC framework and many others still depend on Netty 4.1.x, I think >> we >> > should extract and provide both Netty 4.1 and Netty 4.2 implementations >> for >> > classical transport in 1.2 >> > >> > >> > >> > >> > 何品 >> > >> > >> > PJ Fanning <fannin...@apache.org> 于2025年8月27日周三 17:06写道： >> > >> > > +1 binding >> > > >> > > [x] Download links are valid. >> > > [x] Checksums and signatures. >> > > [x] LICENSE/NOTICE files are ok >> > > [x] No unexpected binary files >> > > [x] All source files have ASF headers >> > > [x] Can compile from source >> > > [x] Can verify the binary build >> > > >> > > On Mon, 25 Aug 2025 at 16:18, kerr <hepin1...@gmail.com> wrote: >> > > > >> > > > +1 >> > > > >> > > > I downloaded and ran the tests locally, it passed, also the last >> commit >> > > are >> > > > there too. >> > > > >> > > > [ 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 >> > > > >> > > > 何品 >> > > > >> > > > >> > > > PJ Fanning <fannin...@apache.org> 于2025年8月25日周一 22:33写道： >> > > > >> > > > > Hello Pekko Community, >> > > > > >> > > > > This is a call for a vote to release Apache Pekko (Core) >> 1.2.0-RC1. >> > > > > >> > > > > The discussion thread: >> > > > > >> > > > > https://lists.apache.org/thread/hjl8jnr3no911188bf110mw7111m9sbt >> > > > > >> > > > > The release candidate: >> > > > > >> > > > > https://dist.apache.org/repos/dist/dev/pekko/1.2.0-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/blob/5b2ae61bf9e41f9dbda595c0ff903ea3ccafecb8/docs/src/main/paradox/release-notes/releases-1.2.md >> > > > > >> > > > > Git tag for the release: >> > > > > >> > > > > https://github.com/apache/pekko/tree/v1.2.0-RC1 >> > > > > Git commit ID: eaf5bc9c9abc25b7b80c5aa8d86b46eb82205315 >> > > > > >> > > > > 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?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 >> > > > > >> > > > > 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 >> > > > > >> > > > 何品 >> > > > >> > > > >> > > > PJ Fanning <fannin...@apache.org> 于2025年8月25日周一 22:33写道： >> > > > >> > > > > Hello Pekko Community, >> > > > > >> > > > > This is a call for a vote to release Apache Pekko (Core) >> 1.2.0-RC1. >> > > > > >> > > > > The discussion thread: >> > > > > >> > > > > https://lists.apache.org/thread/hjl8jnr3no911188bf110mw7111m9sbt >> > > > > >> > > > > The release candidate: >> > > > > >> > > > > https://dist.apache.org/repos/dist/dev/pekko/1.2.0-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/blob/5b2ae61bf9e41f9dbda595c0ff903ea3ccafecb8/docs/src/main/paradox/release-notes/releases-1.2.md >> > > > > >> > > > > Git tag for the release: >> > > > > >> > > > > https://github.com/apache/pekko/tree/v1.2.0-RC1 >> > > > > Git commit ID: eaf5bc9c9abc25b7b80c5aa8d86b46eb82205315 >> > > > > >> > > > > 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?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 >> > > > > >> > > > > 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 >> > > > > >> > > > > >> > > >> > > --------------------------------------------------------------------- >> > > To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org >> > > For additional commands, e-mail: dev-h...@pekko.apache.org >> > > >> > > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org >> For additional commands, e-mail: dev-h...@pekko.apache.org >> >>
