-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is a next release planned? #198
Comments
The only pekko-projection module that isn't released for Scala 3 is pekko-projection-slick. I am hoping to start doing v1.1.0 releases for Pekko modules soon but it could take a while to get to pekko-projection. It requires that we release most of our other modules first. We have v1.1.0-M1 releases for most modules but not for pekko-projection and at this stage, I think the community benefits more from us starting v1.1.0 releases. Releases are non trivial events requiring release management, reviews and votes. So - would you consider switching to pekko-projection-jdbc? If you are stuck with pekko-projection-slick, could you consider building the classes for yourself? On a quick check, I only found 4 source files in src/main plus the reference.conf. |
I see. Thanks for the explanation 🙏 On our side, the goal is to enable team to start to upgrade our projects/services to Scala 3. Since we use other projects that rely on slick, when upgrading those we get a conflict with However, thanks for the suggestion! We will further explore our options. |
I've created an RC and started a vote. There are no guarantees that people will be available to review this RC. https://lists.apache.org/thread/0cwds71rtpzokcpy1v4npkjbkdhtkqow |
It is highly appreciated @pjfanning! Thanks 🙏 |
Did we deprecate this ourselves or was pekko-projection-slick already deprecated by the time we forked Akka? |
Deprecated before we forked. |
I don't know/remember - did we think pekko-projection-jdbc would be sufficient / more suitable for projections? |
1.1.0-M1 is released. It will take a few months to get to a 1.1.0 release because we have to release all the core modules first. |
This is highly appreciated! Thanks a lot to everyone involved 🙏 |
Hey 👋
First of all, thanks for your hard work maintaining this project! It is highly appreciated 🙏
I've noticed that the support for Scala 3 has been merged in #167, however no release has been made with these updates.
Is there a reason for it that I missed? If not, are you planning on releasing in the near future?
Thanks in advance 🙏
The text was updated successfully, but these errors were encountered: