Hi,

+1 (non-binding)

The following items have been checked:
- [x] the links of the package are valid;
- [x] 'incubating' in the name;
- [x] the checksum of the package is valid;
- [x] the signature of the package is valid;
- [x] RELEASE_VERSION in the source code matches the current release;
- [x] DISCLAIMER, LICENSE and NOTICE are not absent, note that we use CI based 
on Skywalking-eyes to check the license;
- [x] no compiled archives bundled in the source archive;
- [x] compile successfully passed under MacOS x86_64.

Regards,
Xiaofeng

On 2022/10/12 11:11:54 Xiguo Hu wrote:
> Hi Apache brpc (Incubating) Community,
> 
> This is a call for vote to release Apache brpc (Incubating) version
> 1.3.0
> 
> [Release Note]
> - Support gcc on linux arm64 by @*gejun*
> *- *Support gcc version >= 11.2.0 by @*wwbmmm *in #1783
> - Support the latest version of bazel(default v4.2.2) by @*hcoona* in #1657
> - Support multi-dimension bvar, a powerful extension of bvar by @
> *serverglen* in #1608
> - Restruct event_dispatcher source file by @*guodongxiaren* in #1888
> - Add http retry with error code policy by @*chenBright *in #1927
> - Add Nacos naming service by @*yyweii *in #1922
> - Add customized server bvar prefix by @*jenrryyou *in #1854
> - Add escape log content before printing by @*gejun*
> *- *Fix issues in FlatMap by @*gejun*
> *- *Fix override issue in pb by @*gejun*, @*wwbmmm*
> *- *Fix ALIGNAS/ALIGNOF/BAIDU_CACHELINE_ALIGMENT by @*gejun*
> *- *Fix some warnings for clang and revert changes on ALIGNAS/ALIGNOF by @
> *gejun*
> *- *Fix rpc_replay continue when failed to init channel by @*ehds* in #1938
> - Fix multi-dimension bvar compile error by @*dabao085 *in #1937
> - Fix bvar_dump_tabs default value problem by @*yyweii *in #1920
> - Fix butex_wait failed with timeout by @*Huixxi *in #1917
> - Fix rpc_replay can't send request equably by @*bumingchun* in #1910
> - Fix compile warning due to DumpOptions object by @*ml-haha* in #1905
> - Fix test_bvar fail on m1 mac by @*wwbmmm *in #1901
> - Fix the slow test in brpc_socket_unittest.cpp by @*zyearn* in #1898
> - Fix the first bthread keytable on worker pthread will be deleted twice by
> @*chenBright* in #1884
> - Fix currently broken MacOS build by @*zyearn* in #1871
> - Fix ProcessHttpRequest supports for http2 by @*dandyhuang *in #1868
> - Fix get_value core caused by the sampler thread start too early by @*Huixxi
> *in #1863
> - Fix UDS ut failed on MacOS by @*wwbmmm *in #1843
> - Fix coredump cause by bad growth_non_responsive http request by @*acelyc111
> *in #1278
> - Fix not to abort when checking the errorno with unicode string by
> @*tobegit3hub
> *in #1142
> Improve/add documents by @*wwbmmm*, @*JackBoosY*, @*morningman*, @
> *serverglen*, @*chenBright*, @*guodongxiaren*, *@xdh0817*, @*KaneVV1*, @
> *tanzhongyi003*, @*lzfhust*, @*Huixxi*
> Fix typos by @*opheliaKyouko*, @*day253*, @*chenBright*, *@fansehep*
> 
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/brpc/1.3.0/
> 
> Git tag for the release:
> https://github.com/apache/incubator-brpc/releases/tag/1.3.0
> 
> Release Commit ID:
> https://github.com/apache/incubator-brpc/commit/a90cf60714941632b2986826336a7c50cbd3d530
> 
> Keys to verify the Release Candidate:
> https://dist.apache.org/repos/dist/dev/incubator/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,
> Huixxi
> 

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

Reply via email to