Pekko Connectors 1.0.1-RC1 is the latest release attempt. There was a scaladoc bug in the 1.0.0 release and there are some upgrades to dependencies.
On 2023/10/23 17:13:43 PJ Fanning wrote: > Pekko Projections 1.0.0 will hopefully be released in the next few days. > There are still 2 repos with no 1.0.0 releases. > > * Pekko Persistence Dynamodb > * Pekko Persistence r2dbc (needs Pekko Projections 1.0.0 release first) > > I propose to create an RC for Dynamodb in next few days. > > Patches Releases? > I think Pekko Connectors 1.0.1 is needed soon. We may need Pekko HTTP 1.0.1 > soon too. > A Pekko Core 1.0.2 could be in the pipeline too. > > > On 2023/10/05 15:13:43 PJ Fanning wrote: > > With Pekko Persistence Cassandra 1.0.0 about to be released, that unblocks > > Pekko Projections 1.0.0 and we should be able to get an RC ready in the > > next week or 2. > > > > Also without 1.0.0 releases: > > * Pekko Persistence Dynamodb > > * Pekko Persistence r2dbc (needs Pekko Projections 1.0.0 release first) > > > > There are also some improvements and bug fixes for existing 1.0.x releases. > > Pekko gRPC 1.0.1-RC1 should be ready for review soon. > > > > After that, we intend to do a Pekko Connectors 1.0.1-RC1 that uptakes Pekko > > gRPC 1.0.1 and that fixes a Scaladoc URL issue that affects downstream > > modules. > > > > There is a known issue in Pekko Persistence Cassandra that we will want to > > fix too. > > > > https://github.com/apache/incubator-pekko-persistence-cassandra/issues/103 > > > > > > On 2023/08/15 07:37:19 Matthew de Detrich wrote: > > > > * Persistence Dynamodb - there is an alternative 3rd party module [2]. > > > Our one works differently. This module is basically ready to release. It > > > doesn't have web site docs buts its README.md has enough detail. > > > > > > Afaik, they are basically completely separate implementations and by that > > > I > > > mean our pekko-persistence-dynamodb has a different table/key-value > > > structure compared to > > > https://github.com/j5ik2o/pekko-persistence-dynamodb. > > > The other major difference is that > > > https://github.com/j5ik2o/pekko-persistence-dynamodb is using the latest > > > version of AWS's Dynamodb async API but this can easily be updated in our > > > own version (albeit in version 1.1.x or 2.0.x, w/e we decide). I am open > > > for adopting https://github.com/j5ik2o/pekko-persistence-dynamodb for > > > 2.0.x > > > but I would like to know if one variant is strictly better than the other > > > (we also need a migration plan). > > > > > > In any case, I think this is the best candidate for a next module release. > > > We can't do such a major change for 1.0.x anyways because people need a > > > migration path from Pekko. > > > > > > > Persistence JDBC - we're waiting on Slick 3.5.0 for Scala 3 support but > > > maybe we should just release it as is and release again when Slick 3.5.0 > > > is > > > out. There is a bit of prep work to do for a release. > > > > > > Similar to my argument for pekko-connectors, I would wait for Slick 3.5.0 > > > but we can do an interim voted on milestone as a compromise > > > > > > > Connectors - this needs gRPC to be released first. Other than that there > > > is the question of Scala 3 support. We have a scala3 where all but 4 > > > connectors have been updated to support Scala 3. At least one other Scala > > > 3 > > > PR is basically ready. There is still a bit of over prep to do before we > > > can release. > > > > > > Answered in > > > https://lists.apache.org/thread/9mh9mbk0ow96yjysfdgw4s151330041p > > > > > > > > > > > > On Sun, Aug 13, 2023 at 9:38 PM PJ Fanning <fannin...@apache.org> wrote: > > > > > > > Pekko Management is released and Pekko gRPC 1.0.0-RC2 is ready for > > > > review. > > > > > > > > Which module do we attempt to release next (order [1])? > > > > > > > > * Persistence Dynamodb - there is an alternative 3rd party module [2]. > > > > Our > > > > one works differently. This module is basically ready to release. It > > > > doesn't have web site docs buts its README.md has enough detail. > > > > * Persistence JDBC - we're waiting on Slick 3.5.0 for Scala 3 support > > > > but > > > > maybe we should just release it as is and release again when Slick > > > > 3.5.0 is > > > > out. There is a bit of prep work to do for a release. > > > > * Connectors - this needs gRPC to be released first. Other than that > > > > there > > > > is the question of Scala 3 support. We have a scala3 where all but 4 > > > > connectors have been updated to support Scala 3. At least one other > > > > Scala 3 > > > > PR is basically ready. There is still a bit of over prep to do before we > > > > can release. > > > > > > > > All the other unreleased modules need the Connectors release to happen > > > > first. > > > > > > > > I propose that we do an RC1 for Persistence Dynamodb early this week. > > > > > > > > [1] > > > > https://cwiki.apache.org/confluence/display/PEKKO/Pekko+Module+Release+Order > > > > [2] https://github.com/j5ik2o/pekko-persistence-dynamodb > > > > > > > > > > > > > > > > On 2023/07/28 09:54:08 PJ Fanning wrote: > > > > > We have a reasonable chance of getting the HTTP and Kafka Connector > > > > modules released next week. > > > > > If that happens, we can move onto to release more modules. > > > > > > > > > > I propose that Pekko Cluster Management is next. Pekko GRPC is > > > > > partially > > > > blocked while we work out how to publish the Gradle Plugin and with > > > > Pekko > > > > Persistence JDBC, we would like to wait for Slick 3.5.0. > > > > > > > > > > Another module that we could consider releasing is the Dynamodb > > > > Persistence module. > > > > > > > > > > See this page for the module dependencies. > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/PEKKO/Pekko+Module+Release+Order > > > > > > > > > > On 2023/06/29 13:33:18 Matthew Benedict de Detrich wrote: > > > > > > PR created at > > > > > > https://github.com/apache/incubator-pekko-http/pull/208 > > > > > > > > > > > > On Thu, Jun 29, 2023 at 10:17 AM Johannes Rudolph < > > > > > > johannes.rudo...@gmail.com> wrote: > > > > > > > > > > > > > Ah, it's about http-cors not http-core :) > > > > > > > > > > > > > > I remember the discussion and the problem. I agree it would be a > > > > > > > good > > > > > > > addition but maybe not a hard blocker for a release of pekko-http > > > > > > > or > > > > > > > pekko-grpc. We can find ways that keeps it out of the critical > > > > > > > path > > > > > > > for now. > > > > > > > > > > > > > > On Thu, Jun 29, 2023 at 10:13 AM Matthew Benedict de Detrich > > > > > > > <matthew.dedetr...@aiven.io.invalid> wrote: > > > > > > > > > > > > > > > > > what is that about and has it been discussed somewhere? > > > > > > > > > > > > > > > > This has been discussed before, main conversation is at > > > > > > > > https://lists.apache.org/thread/qx31xljn6bf7rwcd3kbb9btcdvoxmmwy > > > > and > > > > > > > there > > > > > > > > is also an upstream issue at > > > > > > > > https://github.com/lomigmegard/pekko-http-cors/issues/33. > > > > > > > > > > > > > > > > The tl;dr is that currently pekko-http-cors forms a diamond > > > > dependency > > > > > > > > problem (something that wasn't a concern when it was created > > > > > > > > which > > > > was > > > > > > > > before akka-grpc even existed) and since cors is part of the W3C > > > > standard > > > > > > > > it makes sense for it to be part of pekko-http (alongside that > > > > > > > > its > > > > ultra > > > > > > > > stable and hasn't really changed so it's not really going to add > > > > > > > > maintenance burden) > > > > > > > > > > > > > > > > On Thu, Jun 29, 2023 at 9:38 AM Johannes Rudolph < > > > > > > > johannes.rudo...@gmail.com> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > On Wed, Jun 28, 2023 at 8:00 PM Matthew Benedict de Detrich > > > > > > > > > <matthew.dedetr...@aiven.io.invalid> wrote: > > > > > > > > > > The only thing I feel strongly about is the addition of the > > > > > > > > > pekko-http-core > > > > > > > > > > module to pekko-http in order to remove the diamond > > > > > > > > > > dependency. > > > > > > > > > > > > > > > > > > Hi Matthew, > > > > > > > > > > > > > > > > > > what is that about and has it been discussed somewhere? > > > > > > > > > > > > > > > > > > Johannes > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org > > > > > > > > > For additional commands, e-mail: dev-h...@pekko.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > > > Matthew de Detrich > > > > > > > > > > > > > > > > *Aiven Deutschland GmbH* > > > > > > > > > > > > > > > > Immanuelkirchstraße 26, 10405 Berlin > > > > > > > > > > > > > > > > Amtsgericht Charlottenburg, HRB 209739 B > > > > > > > > > > > > > > > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen > > > > > > > > > > > > > > > > *m:* +491603708037 > > > > > > > > > > > > > > > > *w:* aiven.io *e:* matthew.dedetr...@aiven.io > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org > > > > > > > For additional commands, e-mail: dev-h...@pekko.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > Matthew de Detrich > > > > > > > > > > > > *Aiven Deutschland GmbH* > > > > > > > > > > > > Immanuelkirchstraße 26, 10405 Berlin > > > > > > > > > > > > Amtsgericht Charlottenburg, HRB 209739 B > > > > > > > > > > > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen > > > > > > > > > > > > *m:* +491603708037 > > > > > > > > > > > > *w:* aiven.io *e:* matthew.dedetr...@aiven.io > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > 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 > > > > > > > > > > > > > > -- > > > > > > Matthew de Detrich > > > > > > *Aiven Deutschland GmbH* > > > > > > Immanuelkirchstraße 26, 10405 Berlin > > > > > > Amtsgericht Charlottenburg, HRB 209739 B > > > > > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen > > > > > > *m:* +491603708037 > > > > > > *w:* aiven.io *e:* matthew.dedetr...@aiven.io > > > > > > > --------------------------------------------------------------------- > > 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
