mdedetrich commented on issue #2093: URL: https://github.com/apache/pekko/issues/2093#issuecomment-3261940588
> > Its of course easier to just do all of the API changes in 2.0.x without caring about 1.x, but then it would be a big shock to users. > > Would it? I had assumed it would be mostly source-compatible, perhaps mainly changing some imports? Mostly isn't entirely, and there are more changes aside from imports i.e. `ActorSystem.terminate` for java api is not returning a scala `Future` at all so that isn't source compatible. > > > I don't have an issue in working on main, its actually much easier but then we wouldn't have a nice migration path for users > > I think we have to answer 2 questions: 1) "do we want this change at all", 2) "how do we make this change as smooth as possible for users". I think it would be fine to first work on main so we can answer '1'. If based on that we decide we do want this change in 2.x, then we can see if there's anything we can/should do on the 1.x branch to make the transition smoother. Right, and in my belief the best strategy for figuring out 1 (while also caring about source compatibility) is to actually work on 1.2.x first as I need to actually figure out if its possible. If we don't care about complete source compatibility, then of course I can do a very clean implementation right now on `main` right now but I was under the impression that we wan't an easy migration path which means that for 1.3.x (assuming the actor changes get released then) users get deprecation warnings to change to the `javadsl`/`actordsl` API's but the current actor system works as is, and in 2.0.x the current common actor API won't exist anymore. -- 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]
