pjfanning commented on code in PR #44:
URL: 
https://github.com/apache/incubator-pekko-persistence-jdbc/pull/44#discussion_r1301244343


##########
project/Dependencies.scala:
##########
@@ -8,16 +8,18 @@
  */
 
 import sbt._
+import Keys._
 
 object Dependencies {
   // Keep in sync with .github CI build
   val Scala212 = "2.12.18"
   val Scala213 = "2.13.11"
-  val ScalaVersions = Seq(Scala212, Scala213)
+  val Scala3 = "3.3.0"
+  val ScalaVersions = Seq(Scala212, Scala213, Scala3)
 
   val PekkoVersion = "1.0.0-RC3"
 
-  val SlickVersion = "3.3.3"
+  val SlickVersion = "3.5.0-M4"

Review Comment:
   @MrMaxxan one option would be for you to clone the existing main branch and 
use that code in your project directly or to create a jar. You could try a 
snapshot jar first to see if it works for you.
   
   The priority of Pekko releases is discussed on the [email protected] 
list and noone has yet asked for this module to be released. Have a look 
through the emails at https://lists.apache.org/[email protected]
   
   Apache release process requires that a fair number of people review the 
releases and there are quite a few Pekko repos to release so basically:
   * Pekko Connectors has more people looking for it to be released but there 
are one or two changes still being looked at
   * Other than Slick 3.5 / Scala 3 support, the only thing blocking a 
pekko-persistence-jdbc release is setting up the release notes and related doc 
tasks
       * I'd prefer to wait for Slick 3.5 / Scala 3 support than to release 
what we have as 1.0.0 to cut down on release overhead
       * if there was evidence that Slick 3.5.0 is a ways off yet and that 
there were a number of users waiting on this release, then that might change my 
mind
   * Noone is pressing for any other module releases
   



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to