I think we should so a 1.2.0-M2 release soon. The remaining items in the milestone are more or less ready. https://github.com/apache/pekko/milestone/15
It's nearly 5 months since the 1.2.0-M1 release. After that we need to decide, whether we are in a position to finalise a 1.2.0 release. On 2025/05/27 06:33:05 kerr wrote: > I'm fine, but I want all my new operators included in the 1.2.0-M2 release > 何品 > > > Arnout Engelen <enge...@apache.org> 于2025年5月26日周一 23:37写道: > > > Sounds reasonable to me. > > > > If it's not a problem that things will be a little slower, I'd like to > > RM 1.2.0-M2 and take that as an opportunity to update our release > > process to trigger more of it automatically from CI on tag - which > > should be possible now that we seem to be in good shape with respect > > to reproducibility of the main build. > > > > > > Kind regards, > > > > Arnout > > > > On Mon, May 26, 2025 at 2:04 PM PJ Fanning <fannin...@apache.org> wrote: > > > > > > Hi, > > > There are a pretty large number of changes in the main branch since > > > the 1.2.0-M1 release. There are also some bug fixes in the 1.1.x > > > branch. > > > > > > 1.1.4 milestone > > > https://github.com/apache/pekko/milestone/14 > > > > > > 1.2.0-M2 milestone > > > https://github.com/apache/pekko/milestone/15 > > > > > > I think there are still possibly 1 or 2 changes that would be good to > > > get into 1.1.4, mainly related to some issues that are still popping > > > up when users try mixing Akka and Pekko nodes in a cluster. > > > > > > With 1.2.0, there is still a regular inflow of new streaming API > > > changes - so I don't think we have reached the stage where we can > > > consider a full release. We could release a 1.2.0-M2 release to at > > > least get the existing changes out there. > > > > > > Does anyone have any opinions on this? Is anyone willing to act as > > > release manager for 1 or both of these releases if the consensus is to > > > proceed with them? > > > > > > Thanks, > > > PJ > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org > > > For additional commands, e-mail: dev-h...@pekko.apache.org > > > > > > > > > -- > > Arnout Engelen > > ASF Security Response > > Apache Pekko PMC member, ASF Member > > NixOS Committer > > Independent Open Source consultant > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org > > For additional commands, e-mail: dev-h...@pekko.apache.org > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org For additional commands, e-mail: dev-h...@pekko.apache.org