+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 bundled in source archive.


Best regards,
Guangming Chen

On 2026/01/20 01:54:35 Weibing Wang wrote:
> +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 bundled in source archive.
> 
> 
> Best regards,
> Weibing Wang
> 
> On Sun, Jan 18, 2026 at 11:22 PM Xiaofeng <[email protected]> wrote:
> >
> > Hi Apache bRPC Community,
> >
> > This is a call for vote to release Apache bRPC version 1.16.0
> >
> > [Release Note]
> >
> > Feature:
> > - Support protobuf v30+ compatibility (wrap absl::string_view as 
> > std::string)
> > - Add RISC-V architecture support
> > - Support tag for selective channel
> > - Enable TLS key logging via SSLKEYLOGFILE environment variable
> > - Support more SSL verify modes
> > - Add Couchbase support for CRUD operations
> > - Support naming bthread to help debug
> > - Support dynamic expansion of RDMA block pool
> > - Support shared mbvar and high-performance bvar with babylon counter
> > - Add pthread CPU affinity support
> > - RDMA polling mode enhancement (all messages run in new bthreads)
> > - Add support for checking all living bthreads
> > - Add configurable bthread stack trace signal and timer buckets count
> > - Add pb2json depth limit to prevent stack overflow
> >
> > Bugfix:
> > - Fix C++23 compilation issue
> > - Fix SIGSEGV in read_proc_io during static initialization
> > - Fix SQ overflow bug
> > - Fix TaskTracer deadlocks due to ABA problem
> > - Fix deadlock in SetName (use SetNameSimple instead)
> > - Fix WeightedRandomizedLoadBalancer returns 0 without server
> > - Fix bthread_id_unlock failed in aarch64 CPU
> > - Fix SIMD memory alignment issue in bthread
> > - Fix port parsing validation in str2endpoint
> > - Fix OpenSSL dynamic library link order
> > - Fix various memory and concurrency issues
> >
> > Enhancement:
> > - Remove unused code and BIO for SSL
> > - Fix undefined behaviors in butil library
> > - Improve Bazel configuration settings
> >
> > The release candidates:
> > https://dist.apache.org/repos/dist/dev/brpc/1.16.0/
> >
> > Git tag for the release:
> > https://github.com/apache/brpc/releases/tag/1.16.0
> >
> > Release Commit ID:
> > https://github.com/apache/brpc/commit/37efd2e2b26aa6408fd308490acf14d86713c3fc
> >
> >
> > 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
> >
> > PMC 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 bundled in source archive.
> >
> > Regards,
> > Xiaofeng
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
> 

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

Reply via email to