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

Reply via email to