gharris1727 commented on PR #14220: URL: https://github.com/apache/kafka/pull/14220#issuecomment-1681003739
> I'd just cherry-pick the commit for this PR, but we don't have autogenerated docs for the MM2 properties on those branches, so the wording will have to be different. Yes the backport PRs will need to be different, if only because the 3.6.0 section won't exist. 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. > This will still omit the notes on, e.g., upgrading to 3.4.2, from the main docs page at https://kafka.apache.org/documentation/, but it seems like this is a general issue with our docs. For example, our current trunk's [upgrade notes](https://github.com/apache/kafka/blob/f970ddff10114ae7f9ea1b9966cd25ac8bb5f581/docs/upgrade.html) don't include a section for 3.5.1, even though one is included in the [upgrade notes](https://github.com/apache/kafka/blob/abd1c8e46fc413f8cb8d2d07a80ee74eaf5d9708/docs/upgrade.html) for our current 3.5 branch). Do you think it's worth making a special case for this PR, or is it acceptable to leave upgrade information on older versions (e.g., 3.4.2) off of the docs for newer versions (e.g., 3.5.2)? I agree that seems like a general issue, and I do not think we need to address it here. It looks like the "upgrade to 3.4.2" doesn't already exist and we would need to create it, but we should discuss with others on whether it is appropriate to cherry-pick that section to 3.5/trunk. -- 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
