C0urante commented on PR #14220: URL: https://github.com/apache/kafka/pull/14220#issuecomment-1680894253
> I think that we should copy this line item to the 3.1.x-3.5.x documentation when the patch release for those versions go out, but we might be in danger of forgetting. Can you create blocker tickets with fix versions for the future patch releases that will remind us to document this? Based on our [release policy](https://cwiki.apache.org/confluence/display/KAFKA/Time+Based+Release+Plan#TimeBasedReleasePlan-WhatIsOurEOLPolicy?), it looks like 3.1 and 3.2 are EOL, so it's unlikely we'll need to backport any further than 3.3. I'm also planning on opening a separate PR to backport this to 3.5 (which can then be cherry-picked to 3.4 and 3.3) once this PR is approved. 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. Once those backport commits land, they should be picked up and included in the next releases on those branches automatically. 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)? -- 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
