I think we are ready for this release. If noone objects, I can put together an RC in the next day or 2.
On 2025/11/20 12:52:24 PJ Fanning wrote: > We actually have some worthwhile changes for a pekko-persistence-jdbc 1.2.0 > release now. > We now have DurableState support for MySQL and MariaDB. Turns out that > MariaDB have added some new features that make for a tidier solution in > MariaDB but the contributor also provided a solution for MySQL too. > > https://github.com/apache/pekko-persistence-jdbc/milestone/6 > > One PR is not yet merged. I would appreciate if people could review the new > PRs to see if they think there might be issues. > > I can leave it until next week before attempting an RC. I can act as release > manager but if anyone else wants to do the role, get in touch. > > > On 2025/10/27 02:55:20 kerr wrote: > > I think we can do a release with the default dispatcher change. which can > > be done after pekko 1.3.0 released. > > > > 何品 > > > > > > PJ Fanning <[email protected]> 于2025年10月26日周日 23:03写道： > > > > > I thought that the 1.1.1 changes were unreleased but that version was > > > released in May. > > > So I think we don't need a release after all. There is just 1 small change > > > in the 1.2.0 milestone and I don't think that it isn't sufficient to > > > justify a release. > > > > > > On 2025/10/26 11:06:00 kerr wrote: > > > > +1 for this~ > > > > 何品 > > > > > > > > > > > > PJ Fanning <[email protected]> 于2025年10月26日周日 17:35写道： > > > > > > > > > Hi everyone, > > > > > > > > > > It's been a while since we did a release of this component. > > > > > The unreleased changes are listed in the 2 milestones > > > > > * > > > https://github.com/apache/pekko-persistence-jdbc/milestone/5?closed=1 > > > > > * > > > https://github.com/apache/pekko-persistence-jdbc/milestone/6?closed=1 > > > > > > > > > > If there are no objections to doing a release, I can act as release > > > > > manager. > > > > > If anyone else wants to take on the role, please let us know. > > > > > > > > > > PJ > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: [email protected] > > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
