The core pekko repo [1] has quite a few changes in its main branch that are are targeted at a future 1.1.0 release.
We haven't really agreed on what to do with the code that was already deprecated in the Akka era and there is also the issue of the ApiMayChange annotations on some of the APIs. There are also some new features that developers want to add. We don't have a great deal of developer effort available to us. I suspect that we need to need to balance the need to release some of the 1.1 changes and then maybe try to make another batch of changes in Pekko 1.2. What if we aimed to do a Pekko 1.1.0 release in a few months and said that it was not a Long Term Support release? If we go down this line, we would probably want to have a tentative plan as to when a new LTS release would happen. An example of something that would be useful to release would be the netty4 support. I know that the Apache Flink team would like to use this. Alternatively, we could do a Pekko 1.1.0-M1 release. I suspect that we would end up with a fair number of these and the M version number would discourage uptake (except for testing). What are people's thoughts on the options? [1] https://github.com/apache/incubator-pekko --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
