In the Scala3's community build, apache/pekko always fail, if we can drop scala 2.12, I think we can try to make it pass the community build too. 何品
Nicolas Vollmar <[email protected]> 于2025年9月8日周一 19:38写道： > I am +1 as well for those reasons. > > On Sat, 6 Sept 2025 at 18:52, kerr <[email protected]> wrote: > > > I am +1 on this, we can backport or maintain 1.2.x logger, anyway, this > is > > a open-source project, no hard eol. > > > > I found some code witch is OK both in Scala 2.13 and 3.3 gives unhelpful > > compiling error. To make 2.12 compiles, I spend many time on that, as a > > open source project, we should drop some burdens and put our energy > other > > place. > > > > In a recent pr, I have to rewrite the code in Java to make 2.12 happy. By > > dropping 2.12 , We will have more time to maintain the projects。 > > > > 何品 > > > > PJ Fanning <[email protected]> 于 2025年9月7日周日 上午12:27写道： > > > > > There is GitHub discussion at > https://github.com/apache/pekko/issues/39 > > > > > > We will continue to do Pekko 1.x releases with bug fixes so Scala 2.12 > > > users will not be abandoned. It is just that at some stage, we need to > > > simplify the build and better optimise performance for Scala 2.13 and > 3.x > > > users. > > > > > > Ideally, any comments should be added to the GitHub issue above but > feel > > > free to comment here if that option is not open to you. > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > >
