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

["divijvaidya (via GitHub)" <gi...@apache.org>]

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 solves our requirement of notifying users in advance that Ismael referred to and also pushed official "deprecation" to 3.6.
   
   This blog should talk about Zk removal in 4.0 and should answer the following:
   - what does deprecation mean for users of 3.x (3.6?)
   - what is the migration path to kraft (early access in 3.5 etc.)
   - what is the current (3.5) state of kraft (missing parity features etc.)
   - what is the migration path and what are the tentative timelines
   - what is the EOL security support for last minor version of 3.x (we could point to existing policy if no change)
   - what is the EOL bug support for last minor version of 3.x (we could point to existing policy if no change)
   
   If we don't have consensus on answers to these questions yet, we should discuss them in the community. Ideally, I would like to have a conclusion on the topic of longer EOL support for last minor version in 3.x ([conversation here](https://lists.apache.org/thread/tzx4zkhfz26joq5ydq70bxcfr3zwy1hk)) but fine to post it in the blog as to be decided.
   
   For 3.5, since we didn't post this in the release blog, my preference will be to have a one-time announcement/blog which will contain the snapshot of the living document valid as of v3.5.


-- 
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-unsubscribe@kafka.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org