Hi,

Before vote +1, we must make clear that Category B license including in brpc. I 
found there is one paragraph said on the website[1]. I would like to leave my 
last vote on this issue :-)


“ Unless otherwise specified, all Category B licensed works should be included 
in binary-only form in Apache Software Foundation convenience binaries (and not 
source code). " 


@Justin, Do we have any exception(Unless otherwise specified? ) to include b 
licenses in the source code? 

[1]  https://www.apache.org/legal/resolved.html#weak-copyleft-licenses 
<https://www.apache.org/legal/resolved.html#weak-copyleft-licenses>. 




> On Jan 19, 2020, at 5:20 PM, James Ge <jge...@gmail.com> wrote:
> 
> +1 binding
> 
> Solved issues (many thanks to Justin)
> - Removed butil/memory/scoped_array.h which is replaceable by
> unique_ptr<T[]>
> - Removed butil/md5.cc butil/md5.h test/md5_unittest.cc which is
> replaceable by openssl/md5.h
> - Removed authors from headers
> - Updated copyright years to this year
> - Added appendix in LICENSE
> - Added missing licenses in rapidjson/SVGPan/pprof_perl.cpp etc
> - Replaced crc32 code(category X) in src/brpc/ts.cpp
> - About the supporting function written by Dean Edwards in
> ./src/brpc/builtin/sorttable_js.cpp: apache TrafficControl and spark also
> include the same sortable.js and they only list the MIT licenses [1][2]
> 
> Unsolved:
> - flamegraph_perl(category B), used for displaying CPU/heap/contention
> profiling results in framegraphs.
> 
> [1]
> https://github.com/apache/trafficcontrol/blob/master/licenses/MIT-sorttable
> [2] https://github.com/apache/spark/blob/master/LICENSE#L241
> 
> On Thu, Jan 16, 2020 at 11:56 PM tan zhongyi <zhongyi....@gmail.com> wrote:
> 
>> Hi, guys,
>> 
>> 
>> 
>> 0.9.7-rc03 is ready for vote, here it is.
>> 
>> I am pleased to be calling this vote for the release of  apache
>> brpc(incubating) 0.9.7-rc03.
>> 
>> Btw: there is still some IP issues left, so we add  DISCLAIMER-WIP here.
>> 
>> 
>> The source code can be found at:
>> 
>> 
>> https://dist.apache.org/repos/dist/dev/incubator/brpc/0.9.7-rc03/apache-brpc-0.9.7.rc03-incubating-src.tar.gz
>> 
>> 
>> The release candidate has been tagged in GitHub as 0.9.7-rc03, available
>> here:
>> https://github.com/apache/incubator-brpc/releases/tag/0.9.7-rc03
>> 
>> The SHA-512 checksum is:
>> 
>> 3852185929f8b242aacef5601acb85ab4b397584c515813f740effb1a9eabdba43eaccbe4b5eb1e6763f672fbb4a7937fe71a0dc4a240ef8891d413f30e9b257
>> 
>> 
>> which can be found via:
>> 
>> https://dist.apache.org/repos/dist/dev/incubator/brpc/0.9.7-rc03/apache-brpc-0.9.7.rc03-incubating-src.tar.gz.sha512
>> 
>> 
>> 
>> The signature can be found via:
>> 
>> https://dist.apache.org/repos/dist/dev/incubator/brpc/0.9.7-rc03/apache-brpc-0.9.7.rc03-incubating-src.tar.gz.asc
>> 
>> 
>> 
>> KEYS file is available here:
>> 
>> https://dist.apache.org/repos/dist/dev/incubator/brpc/KEYS
>> 
>> 
>> 
>> 
>> 
>> [Release Note]
>> 
>> 
>> 
>>  *   Add DISCLAIMER-WIP as license issues are not all cleaned
>>  *   Fix many license related issues
>>  *   Health (of a connection) can be checked at rpc-level
>>  *   Fix SSL-related compilation issues on Mac
>>  *   Support SSL-replacement lib MesaLink
>>  *   Support consistent hashing with ketama algo.
>>  *   bvar variables can be exported for prometheus services
>>  *   String[Multi]Splitter supports '\0' as separator
>>  *   Support for bilibili discovery service
>>  *   Improved CircuitBreaker
>>  *   grpc impl. supports timeout
>> 
>> 
>> 
>> 
>> 
>> Please vote on releasing this package as:
>> 
>> Apache brpc(incubating) 0.9.7-rc03
>> 
>> 
>> 
>> This vote will be open until “Jan 19 2020 24:00:00 GMT+0800 (CST)" and
>> 
>> passes if a majority of at least three +1 Apache brpc IPMC votes are
>> 
>> cast.
>> 
>> 
>> 
>> [ ] +1 Release this package
>> 
>> [ ] 0  I don't feel strongly about it, but don't object
>> 
>> [ ] -1 Do not release this package because...
>> 
>> 
>> 
>> Anyone can participate in testing and voting, not just committers, please
>> 
>> feel free to try out the release candidate and provide your votes.
>> 
>> Thanks
>> 
>> 

Reply via email to