Hi, As I proposed in my previous email[1], it's a heat path that our users want to know what features Pulsar provides and at which version they are experimental, beta, or stable.
* Experimental Since indicates a version; since then, the feature has been experimental. Experimental means it is not meant to be used in production yet. * Beta Since indicates a version; since then, the feature has been beta. Beta means you can use it in production, but it still needs battle-testing. * Stable Since indicates a version; since then, the feature has been stable. Stable means it is battle-tested. You can use it in production with full confidence. I made a pull request to initialize the feature matrix page with the proposed structure and attach a preview in the PR thread[2]. Sorting the features we deliver is a good chance to review what we have delivered in the past few years and how much they are away from a product-ready, high-quality functionality. Also, only if we know what features we have, can we start a discussion about the following vision and make a more user-friendly explanation like what Flink does[3] I'm here to call for contributions from all of the community members for commenting the features you know, use, or contribute to the PR linked above[2], with the missing information for when they're experimental, beta, or stable, as well as any documents you ever read or referred to of them. Best, tison. [1] https://lists.apache.org/thread/rrcn3ncqhl5vmm56wgygl921hybgmfgq [2] https://github.com/apache/pulsar-site/pull/720 [3] https://flink.apache.org/roadmap/
