+1 binding

I have checked:

[x] Download links are valid.
[x] Checksums and PGP signatures are valid.
[x] Source code distributions have correct names matching the current release.
[x] LICENSE and NOTICE files are correct for each brpc repo.
[x] All files have license headers if necessary.
[x] No compiled archives are bundled in the source archive.

Best regards
Weibing Wang

On Sat, Jul 13, 2024 at 11:12 PM Xiaofeng <[email protected]> wrote:
>
> Hi Apache bRPC Community,
>
>
> This is a call for vote to release Apache bRPC version 1.10.0
>
>
> [Release Note]
>
>
> Feature:
> - Support connect on socket create (#2574) by @chenBright
> - Support more meta for ServerNode (#2603) by @chenBright
> - Support proxy and generic call of baidu protocol (#2629) by @chenBright
> - Support thread local object iteration (#2632) by @chenBright
> - Support half open state in circuit breaker (#2634) @jiangyt-git
>
> Bugfix:
> - Fix IOBuf profiler rate (#2601) by @chenBright
> - Fix incorrect core file found in run_tests.sh (#2614) by @chenBright
> - Fix FlatMap assign operator bug (#2622) by @chenBright
> - Fix GetProgramName not contains absolute path from cmdline (#2644) by
> @ehds
> - Fix invalid headers of multiple cookie and set-cookie (#2577) by
> @chenBright
> - Fix max concurrency of thrift protocol and nshead protocol (#2613) by
> @chenBright
> - fixbug: there is a ',' before 'quantile=' when labels is empty (#2659)
> @renzhong zhang
> - fix h2 rpc_dump mem leak bug (#2661) by @yanghongchao
> - socket: fix potential double close (#2663) by @Jay
> - Fix uninitialized local side of Socket (#2672) by @chenBright
> - Fix bug: switch between stream_rpc and baidu_std (#2678) by @howarle
> - Fix multi FlatMap scale and size (#2669) by @chenBright
>
> Enhancement:
> - add check for tag range (#2607) by @yanglimingcn
> - bthread set concurrency by tag (#2628) by @yanglimingcn
> - Support SCOPE_EXIT macro (#2643) by @chenBright
> - Opt performance of async log (#2602) by @chenBright
> - Restrict BRPC_VALIDATE_GFLAG to global scope and namespace scope only
> (#2625) by @chenBright
> - Fix comparison warning in http2_rpc_protocol.cpp (#2626) by @imdouyu
> - Add virtual destructors to MongoServiceAdaptor and SpanFilter (#2651)
> - EventDispatcher supports various IO types (#2560) by @chenBright
> - Support FastPthreadMutex contention profiler && expose FastPthreadMutex
> to user (#2589) by @chenBright
> - Reject http request without host (#2600) by @chenBright
> - Support remove old rpcz directory before open (#2610) by @yanglimingcn
> - Add latency scale factor (#2655) by @superhail
> - Add debug log for Socket health check (#2673) by @chenBright
> - Use butil::ThreadLocal to store keytable (#2645) by @MJY-HUST
>
> Others:
> - Fix ci (#2611) by @chenBright
> - Update protobuf version in doc (#2618) by @chenBright
>
>
> Full changes can be found at:
>
> https://github.com/apache/brpc/compare/1.9.0...1.10.0
>
>
> The release candidates:
>
> https://dist.apache.org/repos/dist/dev/brpc/1.10.0/
>
>
> Git tag for the release:
>
> https://github.com/apache/brpc/releases/tag/1.10.0
>
>
> Release Commit ID:
>
> https://github.com/apache/brpc/commit/046fd435c7377af2827349bde71b5736ca172406
>
>
> Keys to verify the Release Candidate:
>
> https://dist.apache.org/repos/dist/dev/brpc/KEYS
>
>
> The vote will be open for at least 72 hours or until the necessary number of
>
> votes are reached.
>
>
> Please vote accordingly:
>
> [ ] +1 approve
>
> [ ] +0 no opinion
>
> [ ] -1 disapprove with the reason
>
>
> MPMC vote is +1 binding, all others are +1 non-binding.
>
>
> Checklist for reference:
>
> [ ] Download links are valid.
>
> [ ] Checksums and PGP signatures are valid.
>
> [ ] Source code distributions have correct names matching the current
> release.
>
> [ ] LICENSE and NOTICE files are correct for each brpc repo.
>
> [ ] All files have license headers if necessary.
>
> [ ] No compiled archives are bundled in the source archive.
>
>
> Regards,
>
> Xiaofeng

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to