I'm not an english speaker, but I still think the unPersistent is not a good name, the `un` means undo or something like that
Maybe PersistenceTestDriver or PersistenceTestHarness ? 何品 PJ Fanning <[email protected]> 于2025年11月10日周一 22:33写道： > I think we may be in a position to create the RC later this week. > There are still a few PRs to merge to 1.3.x but most of those are approved > already. > > One issue that I'd like to discuss is the naming of the Unpersist Behavior > in https://github.com/apache/pekko/pull/2465 > > I, personally, think the name a bit jarring, that it doesn't really > describe the class(es) well. > I would suggest that we just call it Testkit Behavior or something neutral > like that. > > > > On 2025/11/08 19:33:54 kerr wrote: > > Personally, I think we should release Pekko 1.3.0 and Pekko 2.0.0 in > > November. > > > > 何品 > > > > > > kerr <[email protected]> 于2025年11月9日周日 03:31写道： > > > > > I have all my systems running with Java 21, so personally, I don't > want to > > > maintain Java 8 support for now. > > > And want to move to Pekko 2.0.0 soon, which has a clean start. > > > > > > Another concern is, Akka 2.8.0 does support Java 8, and they dropped > Java > > > 8 support in Akka 2.9.0 > > > > > > If we plan to release 1.3.0 soon, we should also prepare to release > 2.0.0. > > > After all, we have already migrated many features from Akka 2.7.0 and > > > included many features unique to Pekko. A new iteration can be > started, and > > > we can release Pekko 2.1.0 in May next year. > > > > > > 何品 > > > > > > > > > PJ Fanning <[email protected]> 于2025年11月9日周日 03:24写道： > > > > > >> I don't personally believe that we need to port everything from Akka > > >> releases as they become available under the Apache license. I would > > >> prefer to concentrate on bug fixes and test coverage. Enhancements if > > >> people want them but I don't think we should grab them without > > >> evidence they are wanted by Pekko users. > > >> > > >> Once Pekko 2.0.0 is out, I don't think we should continue to take Akka > > >> changes over to 1.x unless they fix critical bugs - that they should > > >> only go into 2.x in normal circumstances. > > >> > > >> There is a reasonable chance that Akka 2.8.0 changes will become > > >> Apache licensed before we get to release Pekko 2.0.0. But maybe, it > > >> might focus our minds to get 2.0.0 complete before then. We could then > > >> just add Akka 2.8.0 stuff in a Pekko 2.x release. > > >> > > >> On Sat, 8 Nov 2025 at 20:08, kerr <[email protected]> wrote: > > >> > > > >> > I see, but if we want to support 1.4.0, then we will have much to > port, > > >> eg, > > >> > Akka 2.8.0 needs to be ported to Pekko 1.4.x too . > > >> > And we don't have the same setup, eg, sortImports, Scala versions, > Java > > >> > formatter, and Scala formatter, etc., which causes cherry picking a > huge > > >> > burden. > > >> > While porting recently, I had to do many manual sortings to make the > > >> code > > >> > work with 1.3.x > > >> > > > >> > 何品 > > >> > > > >> > > > >> > PJ Fanning <[email protected]> 于2025年11月9日周日 01:43写道： > > >> > > > >> > > 1.x releases will support Java 8. > > >> > > I'm not going to guess what sort of 1.x releases we will need but > we > > >> > > will continue to do 1.x releases including some small enhancements > > >> > > until 2.0.0 full release happens. After 2.0.0 is out, I think it > is > > >> > > fairly likely that we will only fix bugs in 1.x and this will > likely > > >> > > mean only occasional patch releases. > > >> > > We could easily end up with 1.3.1 or 1.4.0 releases and possibly > > >> beyond. > > >> > > > > >> > > On Sat, 8 Nov 2025 at 14:37, kerr <[email protected]> wrote: > > >> > > > > > >> > > > Is Pekko 1.3.0 the last release that we plan to support Java 8? > > >> > > > > >> > > > --------------------------------------------------------------------- > > >> > > To unsubscribe, e-mail: [email protected] > > >> > > For additional commands, e-mail: [email protected] > > >> > > > > >> > > > > >> > > >> --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: [email protected] > > >> For additional commands, e-mail: [email protected] > > >> > > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
