mdedetrich commented on PR #193: URL: https://github.com/apache/pekko-management/pull/193#issuecomment-2041462134
> but if we insist on calling the next pekko core release 1.1 - then it is completely inconsistent to say this is a breaking change There is no ambiguity to inconsistency when it comes to semantic version. If it breaks ABI/binary compatibility for public API then you increment the major, otherwise you increment the minor. Pekko 1.1.x has zero breaking changes to its public API so there is no debate there, its about the other modules (i.e. pekko-persistence-jdbc, pekko-connectors) where we did break ABI for various reasons where it matters. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
