+1 binding

I've 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.

James Ge

On Sun, Sep 13, 2026 at 4:00 PM Wang,Weibing <[email protected]> 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, Sep 13, 2026 at 11:03 AM Wang Xiaofeng <[email protected]>
> wrote:
> >
> > +1 (non-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.
> >
> > Regards,
> > Xiaofeng
> >
> > On 2026/09/12 15:36:58 Guangming Chen wrote:
> > > Hi Apache bRPC Community,
> > >
> > > This is a call for vote to release Apache bRPC version 1.18.0
> > >
> > > [Release Note]
> > > Highlights (full notes will accompany the GitHub Release):
> > > - Add MySQL client protocol with clean-room auth, text protocol,
> > > transactions and prepared statements by @rajvarun77 (#3330)
> > > - Support TLSv1.3 by @neilxxxxx (#3319)
> > > - Support RDMA handshake protocol V3 by @chenBright (#3350, #3326)
> > > - Support end-to-end ECE negotiation in RDMA handshake V3 by
> @chenBright (#3352)
> > > - Add Power-of-Two-Choices Peak-EWMA (p2c) load balancer by
> @rajvarun77 (#3367)
> > > - Add bounded-load consistent hashing (c_murmurhash_bl) load balancer
> > > by @rajvarun77 (#3502)
> > > - Support Protobuf v35 by @wasphin (#3429)
> > > - Support flow-controlled gRPC client requests by @wasphin (#3430)
> > > - Add TLS peer name verification for clients by @wwbmmm (#3408)
> > > - Interconnect via UBShmTransport based on LD/ST shared-memory
> > > semantics by @zchuango (#3290)
> > > - Harden HTTP/2 receive path against unbounded resource growth by
> > > @wwbmmm (#3474)
> > > - Reject HTTP/1 header forms that desync framing by @chenBright (#3521)
> > > - Add RISC-V Zvbc vector CRC32C acceleration by @Felix-Gong (#3332)
> > >
> > > The release candidates:
> > > https://dist.apache.org/repos/dist/dev/brpc/1.18.0/
> > >
> > > Git tag for the release:
> > > https://github.com/apache/brpc/releases/tag/1.18.0
> > >
> > > Release Commit ID:
> > >
> https://github.com/apache/brpc/commit/94f1bbd32845a45f0218dfe43e25791252bdcb72
> > >
> > > 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,
> > > Guangming Chen
> > >
> > > ---------------------------------------------------------------------
> > > 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