C0urante commented on PR #14220: URL: https://github.com/apache/kafka/pull/14220#issuecomment-1682432780
> I was thinking that in addition to this upgrade note, we would also need to backport the configuration documentation to keep the links valid, and because the documentation would be incomplete without the new configuration present. That would need a delayed-merge PR against kafka-site instead of merging to kafka today. Ah, I see. I wasn't planning on backporting the complete config docs (IMO it's too high-risk to backport the config autogeneration logic), I was planning on tweaking the [older docs on MM2's properties](https://github.com/apache/kafka/blob/abd1c8e46fc413f8cb8d2d07a80ee74eaf5d9708/docs/ops.html#L768-L788) and linking to those in the release notes. I've filed https://github.com/apache/kafka/pull/14235 to demonstrate. @gharris1727 since I've created the backport PR, do you think it would be safe to merge this PR (assuming wording and formatting are satisfactory) and continue discussing a backport strategy on the backport PR? -- 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: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
