Skip to content

Conversation

shashankhs11
Copy link
Contributor

@shashankhs11 shashankhs11 commented Aug 8, 2025

Updated Kafka Streams configuration documentation to stay latest with
version 4.0.0.

Reviewers: Matthias J. Sax [email protected]

@github-actions github-actions bot added triage PRs from the community docs small Small PRs labels Aug 8, 2025
@github-actions github-actions bot removed the triage PRs from the community label Aug 16, 2025
@mjsax mjsax added the streams label Aug 16, 2025
@mjsax mjsax merged commit 6562427 into apache:trunk Aug 17, 2025
36 of 38 checks passed
mjsax pushed a commit that referenced this pull request Aug 17, 2025
Updated Kafka Streams configuration documentation to stay latest with
version 4.0.0.

Reviewers: Matthias J. Sax <[email protected]>
mjsax pushed a commit that referenced this pull request Aug 17, 2025
Updated Kafka Streams configuration documentation to stay latest with
version 4.0.0.

Reviewers: Matthias J. Sax <[email protected]>
@mjsax
Copy link
Member

mjsax commented Aug 17, 2025

Thanks for the PR. Merged to trunk and cherry-picked to 4.1 and 4.0 branches. -- Not sure if we will get new RC for 4.1, but I assume next 4.0.1-rc should pick it up. I'll keep monitoring. Maybe we need a PR for kafka-site in addition if changes are not picked up.

\cc @mimaison and @clolov as RMs.

For the 4.1 updates you mentioned on the Jira ticket, let's do a new PR.

@shashankhs11
Copy link
Contributor Author

Thank you for the merge!

Maybe we need a PR for kafka-site in addition if changes are not picked up.

Yes, please let me know if you require me to do something later.

I just saw your comment on the Jira but I somehow missed the notification. I'll soon create a new PR for the 4.1 updates. Thanks!

@shashankhs11 shashankhs11 deleted the KAFKA-15307 branch August 21, 2025 21:04
@mimaison
Copy link
Member

Have all the changes you wanted to include in 4.1 merged? If not, can you do them in the next 24 hours or so? I'm about to start making a new RC, and I won't wait for cleanups in the docs. We can update the website after the release if needed.

@shashankhs11
Copy link
Contributor Author

Hi @mimaison, I'll raise a new PR with the 4.1 changes within the next 6 hours, which hopefully gives enough time to review before merging. I hope this sounds good.

@mjsax
Copy link
Member

mjsax commented Aug 26, 2025

Thanks @shashankhs11 -- please ping for review on the new PR when you have it ready.

@shashankhs11
Copy link
Contributor Author

Hi @mjsax, apologies for the delay and not pushing as promised. Here is the new PR #20408, ready for review!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants