Release Proposal for Apache Kvrocks 2.11.0

[PragmaTwice]

It has been approximately 3 months since the last release v2.10.1, with numerous new features and fixes merged into the unstable branch. I am now proposing the next release, version 2.11.0.

All commits on the unstable branch until 571b022 (included) will be considered as commits for this release, including search commands (FT.*).

The deadline for the cherry-picking period has been set as Jan 22, 2025, at 12:00 UTC+0. No new commits will be accepted after this time.

Feel free to leave your comments about this release proposal.

For the release process, please refer to: https://kvrocks.apache.org/community/create-a-release

@apache/kvrocks-committers

[torwig]

+1 from me.

[git-hulk]

+1

[aleksraiden]

+1

[Beihao-Zhou]

+1

[adulau]

+10 !

[Yangsx-1]

+1

[PragmaTwice]

Hmm, should we ship #2721 in 2.11.0? cc @git-hulk @rabunkosar-dd

As in the release guide, we can decide to ship if it's necessary, with a reason. So I would like to ask if you have an opinion.

[rabunkosar-dd]

It would be good to ship. We have been working on root-causing some high tail-end latencies reported by clients, this will help a lot to see the server side metrics, I also have a PR to support this in the kvrocks_exporter to get the prometheus metrics

[git-hulk]

Thanks for @PragmaTwice raising this. I'm good to ship this feature since it would be helpful to allow observing the latency with the histogram instead of only an average value.

I also have a PR to support this in the kvrocks_exporter to get the prometheus metrics

@rabunkosar-dd Thanks for your contribution again. I saw this PR and will take a look and try soon.

[PragmaTwice]

Thank you for your opinion. I'll include this commit.

[PragmaTwice]

The official release vote thread: https://lists.apache.org/thread/ffb1tl09c2p4s7ybrvv1wqtn09dq3ofp