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 have a concern with marking Zk as deprecated starting 3.5. But I do want to ensure that the manner in which we convey it covers potential FAQs and demonstrates a path forward to the users. We don't (correct me if I am wrong) publish timeline for 4.0 release anywhere except nested inside a KIP which has a misleading title. From the title, I would expect the KIP to talk about state of kraft production readiness and not Zk deprecation. Kraft production readiness is an independent topic than Zk deprecation. That is why I think we should have a separate KIP/living document for Zk deprecation timeline and a more verbose communication to the users (instead of one line in this announcement). We can either expand on the existing blog post or I would be happy to volunteer to write a new one once everyone is in agreement (I don't have a strong opinion either ways). -- 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: dev-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
