pjfanning commented on code in PR #256: URL: https://github.com/apache/incubator-pekko/pull/256#discussion_r1143372895
########## docs/src/main/paradox/common/binary-compatibility-rules.md: ########## @@ -60,15 +54,17 @@ Some modules are excluded from the binary compatibility guarantees, such as: ### When will a deprecated method be removed entirely -Once a method has been deprecated then the guideline* is that it will be kept, at minimum, for one **full** minor version release. For example, if it is deprecated in version 2.5.2 then it will remain through the rest of 2.5, as well as the entirety of 2.6. +Once a method has been deprecated then the guideline* is that it will be kept, at minimum, for one **full** minor version release. For example, if it is deprecated in version 1.0.2 then it will remain through the rest of 1.0, as well as the entirety of 1.1. + +Methods that were deprecated in Akka, before the project fork to Pekko, are being considered for removal in Pekko 1.1.0. Review Comment: Since the current text in this PR is non-commital, could we consider it as a useful guideline. I'd prefer to not vote on the deprecations until we are planning a v1.1.0 release. Circumstances might have changed by then and it would be useful to vote based on that. For instance, we might get a lot of feedback from Pekko users saying the Akka to Pekko switchover was hard and that they would appreciate if we don't remove methods in v1.1.0. -- 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]
