tison

This patch can work, but we may think a bit more on the CLI arguments part - how to pass the option. ```patch diff --git a/tests/gocase/util/server.go b/tests/gocase/util/server.go index d0ab1b7..3c80ec8 100644...

Closed as information delivered. We don't open a generic issue like this. Only file issues if we have concrete actionable tasks for improving the website.

@aleksraiden I suggest you start a discussion about upgrading the C++ standard in the Discussion forum. It's not an actionable task (for now) but an open-ended discussion. Also, answering in-thread...

I suggest you start a discussion on [email protected] first. This is not a trivial improvement but which suite we'd prefer. I'll close this pull request before we reach a consensus.

@mattisonchao I just notice we already use awaitility in curator-client https://github.com/apache/curator/pull/389. Then I'm OK to continue the patch.

@mattisonchao if you'd like to continue it, please merge master and ping me for review.

No activities. Closed.

Thanks for starting this discussion @DonghunLouisLee! Generally, client libraries should be backward compatible during a major version. And I can see that the `pulsar` crate already takes versions from `0.x`...

BTW, the Pulsar protocol has a [protocol version property](https://github.com/apache/pulsar/blob/a4990f828f208483d07bd3971e5ad4719109b32d/pulsar-common/src/main/proto/PulsarApi.proto#L241) to help us determine what features are available in the target cluster. It helps us do version controlling, like throwing a...

But yes, we can target the next release to be compatible (tested) with Pulsar 2.10.x only, and later extend its compatible matrix, while we may call it 4.2.0 or 5.0.0...