[GitHub] [kafka-site] divijvaidya commented on pull request #528: MINOR: Add statmenet about ZK deprecation to 3.5 release blog post

2023-06-26 Thread via GitHub
divijvaidya commented on PR #528: URL: https://github.com/apache/kafka-site/pull/528#issuecomment-1607874433 > I believe the most important points are the following: - update the blog post (with minimum information and link to the docs) - update the docs with ZK deprecation section

[GitHub] [kafka-site] divijvaidya commented on pull request #528: MINOR: Add statmenet about ZK deprecation to 3.5 release blog post

2023-06-21 Thread via GitHub
divijvaidya commented on PR #528: URL: https://github.com/apache/kafka-site/pull/528#issuecomment-1601385284 > I still think our users are better off if we update the announcement and docs now vs a few months later. Can someone explain why the latter would be better? For me, I don't

[GitHub] [kafka-site] divijvaidya commented on pull request #528: MINOR: Add statmenet about ZK deprecation to 3.5 release blog post

2023-06-21 Thread via GitHub
divijvaidya commented on PR #528: URL: https://github.com/apache/kafka-site/pull/528#issuecomment-1601303527 IMO, we should have a living document "Zk deprecation roadmap" which is updated with every release. Every release blog post will have a section pointing to this document. This