Hi, I'd like to pitch the idea of just merging the pekko-http scala3 support to main branch when it is ready and including this in the v1.0.0 release. We have already made small-ish changes like using Parboiled jar and upgrading Jackson.
The scala3 changes don't make significant changes to the APIs and it feels like adding the scala3 support now would not make migration from Akka HTTP much harder. Akka HTTP has released scala3 support (BSL licensed) but the release seems to have gone smoothly - without much user complaint. Nothing significant had to be documented about the migration to Akka HTTP 10.4 [1]. My main reason for supporting an early merge of this is that it will save us a whole circle of releases downstream. A scala3 support pekko-http v1.1.0 would lead to new releases for pekko-connectors and other downstream projects. I get that we want to make migration to v1.0.0 easy but I don't think the scala3 changes make this significantly harder. If we had made faster progress with the v1.0.0 release then being conservative probably makes sense but now that we still don't have a release scheduled, it feels like we might be better off planning to get a slightly bigger v1.0.0 release done and saving ourselves the hassle of having to do a v1.1.0 release for the scala3 changes. [1] https://doc.akka.io/docs/akka-http/current/migration-guide/migration-guide-10.4.x.html#general-notes --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
