Hi everyone, Due to a class name issue [1], we are planning to produce an RC1 for Pekko 1.0.1 over the next day or two.
So far the issue appears in compatibility testing for Scala 3.3.2-RC1 and hasn't been reported elsewhere. The class in question is in pekko-remote. The code is package private so I don't think it will cause major issues when we get 1.0.1 released (i.e. users switching from v1.0.0 to v1.0.1 are very unlikely to have any issues relating to us changing the problematic class name). There is nothing in the `main` branch yet that we wouldn't want to include in the v1.0.1 release so we will make the RC from the `main` branch. I still think we can also press on with a Pekko HTTP 1.0.0-RC1 in the coming days. We might delay it by a couple of days but I think we can release Pekko HTTP 1.0.0 with a dependency on Pekko (Core) 1.0.0 but release note that users should use Pekko (Core) 1.0.1 when it is available. The alternative is to delay Pekko HTTP 1.0.0-RC1 until Pekko (Core) 1.0.1 is released. With the current 2 phase voting requirements and the build process that we have, that probably means delaying Pekko HTTP 1.0.0-RC1 by 2 weeks. Feel free to share your opinions on this thread. Regards, PJ [1] https://github.com/apache/incubator-pekko/issues/491 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org For additional commands, e-mail: dev-h...@pekko.apache.org
