Re: [VOTE] Release Apache ECharts (incubating) 4.1.0.rc3

[Mike Jumper]

On Sun, May 20, 2018 at 10:07 PM, SHUANG SU  wrote:

> Thanks, Justin,
>
> I think I should remove the jar about rat from the artifact, and then
> there is no binary code anymore.
>
> But I am puzzled about the definition of the term "compiled code".
> Generally, the JavaScript code does not need to be compiled to binary. The
> code in "dist/**" is also JavaScript code, which is combined to some single
> files and some of them are minified. And the ".map" file is provided for
> mapping each term of the combined code to the original code in src/**.
> Without or without the ".map", the combined code can be checked. I think
> this kind of combined code is not "compiled code" ...


It's not purely about being able to check things, nor about how you define
the word "compiled". You also need to be able to make changes. From
http://www.apache.org/legal/release-policy.html#compiled-packages :

"... All releases are in the form of the source materials needed to make
changes to the software being released. ..."

In the sense that the original source has been passed through a tool that
mangled it into a form that can't be readily modified, it's not source,
even if you don't want to call it "compiled".

- Mike

Re: [VOTE] Release Apache ECharts (incubating) 4.1.0.rc3

[SHUANG SU]

Thanks, Justin,

I think I should remove the jar about rat from the artifact, and then there
is no binary code anymore.

But I am puzzled about the definition of the term "compiled code".
Generally, the JavaScript code does not need to be compiled to binary.
The code in "dist/**" is also JavaScript code, which is combined to some
single files
and some of them are minified. And the ".map" file is provided for mapping
each term
of the combined code to the original code in src/**. Without or without the
".map",
the combined code can be checked.
I think this kind of combined code is not "compiled code", but I don't know
the formal definition
about this case.

Thanks,
Shuang




--
 Su Shuang (100pah)
--


2018-05-21 5:31 GMT+08:00 Justin Mclean :

> Hi,
>
> Releases at the ASF must not contain compiled code. You can if you want
> also produce a conviance binary for users at the same time but the source
> release needs to contain no compiled code otherwise it's not open source.
>
> Thanks,
> Justin
>
> On Mon., 21 May 2018, 7:10 am SHUANG SU,  wrote:
>
> > Thanks, Willem.
> >
> > But I will explain the reason that provides an all-in-one artifact.
> >
> > I understand that one of the reasons for separating src and binary files
> > is that in some project the compilation is depending on the target
> runtime
> > environment and thus the products cannot be enumerated completely.
> > The other reason might be that the binary files are different to be
> > checked.
> > (Am I correct? or miss something notable?)
> >
> > But in this kind of JavaScript program, the built products is environment
> > independent and can be enumerated completely.
> >
> > And the build products of the JavaScript project is text-based, which can
> > be
> > checked basically.
> >
> > Moreover, there are too many approaches to require and use a JavaScript
> > project.
> > First of all, a user project may be a browser project or run on
> > a server (Node.js) or both.
> > Both in those runtime environments, the user project may need to
> required a
> > pre-combined
> > built file via AMD or CommonJS module loader or global variable or some
> > bundle tools like
> > Webpack and rollup.js (provided in dist/**).
> > Or the user project may intent to require files separately on demand via
> > CommonJS
> > or some bundle tools like Webpack and rollup.js (provided in lib/**).
> > Or the user project may intent to require files via ES module loader
> > (provided in src/**).
> > During the development of user projects, probably more than one
> approaches
> > are needed.
> >
> > So we both provide those files all-in-one in the artifacts for the
> > convenience of the users.
> > And this way follows the convention of most of the JavaSript libs, and it
> > works well for years in
> > the ECharts community.
> >
> >
> > Truly,
> > Su Shuang
> >
> >
> >
> > --
> >  Su Shuang (100pah)
> > --
> >
> >
> > 2018-05-21 0:25 GMT+08:00 Kevin A. McGrail :
> >
> > > If the release candidate isn't correct for the artifacts you need to
> roll
> > > an rc4 which might be two files not one and send that for a vote.
> > >
> > > On Sat, May 19, 2018, 22:34 Willem Jiang 
> wrote:
> > >
> > > > Hi,
> > > >
> > > > As there is only one zip file, I guess it just the src distribution.
> > > > But after went through the file, I found lot of echart js files in
> the
> > > dist
> > > > directory and the rat jar.
> > > >
> > > > So I'm confused what's the purpose of apache-echarts-4.1.0.rc3-
> > > > incubating.zip
> > > >
> > > > Normally we distribute the src and binary files separately.
> > > >
> > > >
> > > >
> > > > Willem Jiang
> > > >
> > > > Blog: http://willemjiang.blogspot.com (English)
> > > >   http://jnn.iteye.com  (Chinese)
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
> > > >
> > > > On Thu, May 17, 2018 at 7:42 PM, SHUANG SU 
> > > wrote:
> > > >
> > > > > I am pleased to be calling this vote for the release of Apache
> > ECharts
> > > > > 4.1.0.rc3.
> > > > >
> > > > > Apache ECharts community has voted and approved the release.
> > > > >
> > > > > Vote thread:
> > > > > https://lists.apache.org/thread.html/
> 67dffef28ecffd66689ac991ca027c
> > > > > 0868d734629949d958e7b12dd3@%3Cdev.echarts.apache.org%3E
> > > > >
> > > > > Results thread:
> > > > > https://lists.apache.org/thread.html/
> 3a6e627a7e07d5de0856296d44bb40
> > > > > 8e17ee6795cc74ef190a7a5d23@%3Cdev.echarts.apache.org%3E
> > > > >
> > > > > The release candidate to be voted over is available at:
> > > > > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.
> 1.0.rc3/
> > > > >
> > > > > The release candidate is signed with a GPG key available at:
> > > > > https://dist.apache.org/repos/dist/dev/incubator/echarts/KEYS
> > > > >
> > > > > A tagged git 

Re: [VOTE] Retire the Slider podling

[Hen]

+1.

Kudos to the podling for voting for retirement. The JIRA gives hope that
there is user activity, but if the lack of commits and existence of a
technical alternative in Hadoop suggests this is a good decision.

Hen


On Sun, May 20, 2018 at 10:59 AM, Billie Rinaldi  wrote:

> After a long period of low activity, the Slider PPMC has recently decided
> upon retirement [1]. Please vote on whether we should retire the Slider
> podling. Here is my +1 (binding).
>
> [ ] +1 Retire Slider
> [ ] +0 No opinion
> [ ] -1 Do not retire Slider because ...
>
> This vote will remain open for 72 hours.
>
> [1]: https://s.apache.org/V8SB
>

Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.2 [RC1]

[Willem Jiang]

Hi,

I did some check on the source zip and binary zip, the License and Notice
files looks good. But I also found some issues here.
As I cannot build the binary without doing some changes on the pom file, I
had to vote -1 (binding) here.

Here are the issues that I found:

1. there is bunch of dubbo-2.6.2-SNAPSHOT  in the pom.xml file, I guess the
maven release plugin doesn't take all of them.
.//bom/pom.xml:  dubbo-2.6.2-SNAPSHOT
.//dependencies-bom/pom.xml:  dubbo-2.6.2-SNAPSHOT
.//distribution/pom.xml:2.6.2-SNAPSHOT-SNAPSHOT
.//pom.xml:  dubbo-2.6.2-SNAPSHOT

2. I checked the source zip[1], it is not same with github tag one[2].
There are some log files and empty directories which is not in the git
repo, I guess it relates to the builder's workspace.
It could be addressed by generate the source release kit in the
distribution like we did here[3].
BTW, it's quite important that every one can build the kit by following the
instruction. I didn't found the instruction file from the README.

3. I tried to build the source from kit, it looks the check style is
enabled when since JDK 1.8 and I just got the out of memory error there.
I found there are comment about this check style issue (it takes lots of
time and it doesn't work on my box). So I created an issue[4] of it.
I can build the source by modify the pom to skip the check style check, but
it kind of hiking , so I had to vote -1 (binding) for it.

4. I checked the binary kit, it only includes the jars file of dubbo[5], as
we cannot provide the apache maven release now, it could cause some trouble
for the user to consume the binary without third party dependencies. Do we
have any plan for it ?

Another tip for the release check is running some applications which is
build on the top of the framework to make sure all the distribution is good.


[1]
https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.2/dubbo-incubating-2.6.2-source-release.zip
[2]https://github.com/apache/incubator-dubbo/archive/dubbo-2.6.2.zip
[3]
https://github.com/apache/incubator-servicecomb-saga/blob/master/saga-distribution/src/assembly/src.xml
[4]https://github.com/apache/incubator-dubbo/issues/1821
[5]
https://github.com/apache/incubator-dubbo/blob/2.6.2-release/distribution/src/assembly/release-bin.xml#L43



Willem Jiang

Blog: http://willemjiang.blogspot.com (English)
  http://jnn.iteye.com  (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem

On Fri, May 18, 2018 at 5:26 PM, Jun Liu  wrote:

> Hello All,
>
> This is a call for vote to release Apache Dubbo (Incubating) version 2.6.2.
>
> The Apache Dubbo community has voted on and approved a proposal to release
> Apache Dubbo (Incubating) version 2.6.2.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Apache Dubbo™ (incubating) is a high-performance, java based, open source
> RPC framework. Dubbo offers three key functionalities, which include
> interface based remote call, fault tolerance & load balancing, and
> automatic service registration & discovery.
>
> Dubbo vote thread:
> https://lists.apache.org/thread.html/2292dfa6698c97550419ca547c8cd9
> 71bae8c88c440ef277314c841f@%3Cdev.dubbo.apache.org%3E
>
> Dubbo vote result thread:
> https://lists.apache.org/thread.html/701b3d436920eea3030f2a977eb1d3
> 826774bc96e0b1d8b1d09a2ce8@%3Cdev.dubbo.apache.org%3E
>
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.2
>
> Git tag for the release:
> https://github.com/apache/incubator-dubbo/tree/dubbo-2.6.2
>
> Hash for the release tag:
> afab04c53edab38d52275d2a198ea1aff7a4f41e
>
> Release Notes:
> https://github.com/apache/incubator-dubbo/blob/2.6.2-release/CHANGES.md
>
> The artifacts have been signed with Key : 28681CB1, which can be found in
> the keys file:
> https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS
>
> The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks.
> Jun Liu,
> The Apache Dubbo (Incubating) Team
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 4

[Willem Jiang]

Hi Matteo,

The PR looks good. I really like the script that does the check.
Please make sure you run it as a routine to verify the release kit.


Willem Jiang

Blog: http://willemjiang.blogspot.com (English)
  http://jnn.iteye.com  (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem

On Mon, May 21, 2018 at 8:32 AM, Matteo Merli 
wrote:

> Willem, thanks for catching these issues.
>
> I have fixed the missing dependencies, specified the exact version of each
> of them
> and added a script to validate that new changes won't break it later.
> https://github.com/apache/incubator-pulsar/pull/1820
>
> I will cancel this vote and create a new candidate.
>
> Matteo
>
> On Sat, May 19, 2018 at 11:12 PM Willem Jiang 
> wrote:
>
> > Hi,
> >
> > As there are some License issues in the binary distribution (please check
> > the section4 for more information), I had to vote  -1 (binding).
> >
> > Here are the verifications which I did
> > 1. check the checksums and verify the KEY.
> >   These KEY are not signed by the others, so I got the warning WARNING:
> > This key is not certified with a trusted signature!
> >
> > 2. Checked the License and Notice file of the source distribution.
> >   It looks good.
> >
> > 3. Built the source with instruction of README and start the server
> >   It works and I can start the standalone server.
> >   I also checked the distribution file in the all directory, I can get
> the
> > binary and source distribution there.
> >
> > 4. Checked the License and Notice file of the binary distribution.
> > There is not version of bundled jars specified in the License file. It
> > could cause some trouble as the License could be changed in different
> > versions of jar distribution.
> >
> >  Most of the bundled jars are specified in the License file, but some of
> > them are missed.
> >
> > * com.google.errorprone-error_prone_annotations-2.0.19.jar
> >
> > * com.google.instrumentation-instrumentation-api-0.4.3.jar
> >
> > * com.squareup.okhttp-okhttp-2.5.0.jar
> >
> > * com.squareup.okio-okio-1.6.0.jar
> >
> > * org.apache.distributedlog-distributedlog-core-shaded-4.7.0.jar
> >
> > The javassist jar is not CDDL license, it has multiple licenses
> > ASL,LGPL,MPL (we need to pick one of them).
> >
> > * org.javassist-javassist-3.21.0-GA.jar
> >
> >
> > Willem Jiang
> >
> >
> > On Fri, May 18, 2018 at 11:35 AM, Matteo Merli 
> wrote:
> >
> > > This is the fourth release candidate for Apache Pulsar, version
> > > 2.0.0-rc1-incubating.
> > >
> > > Pulsar is a highly scalable, low latency messaging platform running on
> > > commodity hardware.
> > > It provides simple pub-sub semantics over topics, guaranteed
> > at-least-once
> > > delivery of
> > > messages, automatic cursor management for subscribers, and
> > geo-replication.
> > >
> > > Link to the voting thread on pulsar dev list:
> > > https://lists.apache.org/thread.html/865ac7e993265a31512642c5f29e53
> > > e65f4199b931a5ae91d07fba77@%3Cdev.pulsar.apache.org%3E
> > >
> > > It fixes the following issues:
> > > https://github.com/apache/incubator-pulsar/milestone/12?closed=1
> > >
> > > *** Please download, test and vote on this release. This vote will stay
> > > open
> > > for at least 72 hours ***
> > >
> > > Note that we are voting upon the source (tag), binaries are provided
> for
> > > convenience.
> > >
> > > Source and binary files:
> > > https://dist.apache.org/repos/dist/dev/incubator/pulsar/
> > > pulsar-2.0.0-rc1-incubating-candidate-4/
> > >
> > > SHA-1 checksums:
> > > a959a33500508d0ba690ca177eb39cf83dddf022
> > > apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz
> > > 5b9bedd2f284c5a8d95ba6dc3c70af8c266fbb3b
> > > apache-pulsar-2.0.0-rc1-incubating-src.tar.gz
> > >
> > > Maven staging repo:
> > > https://repository.apache.org/content/repositories/
> orgapachepulsar-1014/
> > >
> > > The tag to be voted upon:
> > > v2.0.0-rc1-incubating-candidate-4 (e5d3bda9607703c2e012983c7ef64f
> > > 5eb4118de7)
> > > https://github.com/apache/incubator-pulsar/releases/tag/
> > > v2.0.0-rc1-incubating-candidate-4
> > >
> > > Pulsar's KEYS file containing PGP keys we use to sign the release:
> > > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
> > >
> > > Please download the the source package, and follow the README to build
> > > and run the Pulsar standalone service.
> > > --
> > > Matteo Merli
> > > 
> > >
> >
> --
> Matteo Merli
> 
>

[IP CLEARANCE] Arrow Ruby Library

[Wes McKinney]

Apache Arrow is receiving a code donation of a Ruby language library [1].

Please vote to approve this contribution.

This is a lazy consensus majority vote, per the IP clearance process
[2], open for at least 72 hours.

Wes

[1] http://incubator.apache.org/ip-clearance/arrow-ruby-library.html
[2] http://incubator.apache.org/ip-clearance/

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 4

[Matteo Merli]

Willem, thanks for catching these issues.

I have fixed the missing dependencies, specified the exact version of each
of them
and added a script to validate that new changes won't break it later.
https://github.com/apache/incubator-pulsar/pull/1820

I will cancel this vote and create a new candidate.

Matteo

On Sat, May 19, 2018 at 11:12 PM Willem Jiang 
wrote:

> Hi,
>
> As there are some License issues in the binary distribution (please check
> the section4 for more information), I had to vote  -1 (binding).
>
> Here are the verifications which I did
> 1. check the checksums and verify the KEY.
>   These KEY are not signed by the others, so I got the warning WARNING:
> This key is not certified with a trusted signature!
>
> 2. Checked the License and Notice file of the source distribution.
>   It looks good.
>
> 3. Built the source with instruction of README and start the server
>   It works and I can start the standalone server.
>   I also checked the distribution file in the all directory, I can get the
> binary and source distribution there.
>
> 4. Checked the License and Notice file of the binary distribution.
> There is not version of bundled jars specified in the License file. It
> could cause some trouble as the License could be changed in different
> versions of jar distribution.
>
>  Most of the bundled jars are specified in the License file, but some of
> them are missed.
>
> * com.google.errorprone-error_prone_annotations-2.0.19.jar
>
> * com.google.instrumentation-instrumentation-api-0.4.3.jar
>
> * com.squareup.okhttp-okhttp-2.5.0.jar
>
> * com.squareup.okio-okio-1.6.0.jar
>
> * org.apache.distributedlog-distributedlog-core-shaded-4.7.0.jar
>
> The javassist jar is not CDDL license, it has multiple licenses
> ASL,LGPL,MPL (we need to pick one of them).
>
> * org.javassist-javassist-3.21.0-GA.jar
>
>
> Willem Jiang
>
>
> On Fri, May 18, 2018 at 11:35 AM, Matteo Merli  wrote:
>
> > This is the fourth release candidate for Apache Pulsar, version
> > 2.0.0-rc1-incubating.
> >
> > Pulsar is a highly scalable, low latency messaging platform running on
> > commodity hardware.
> > It provides simple pub-sub semantics over topics, guaranteed
> at-least-once
> > delivery of
> > messages, automatic cursor management for subscribers, and
> geo-replication.
> >
> > Link to the voting thread on pulsar dev list:
> > https://lists.apache.org/thread.html/865ac7e993265a31512642c5f29e53
> > e65f4199b931a5ae91d07fba77@%3Cdev.pulsar.apache.org%3E
> >
> > It fixes the following issues:
> > https://github.com/apache/incubator-pulsar/milestone/12?closed=1
> >
> > *** Please download, test and vote on this release. This vote will stay
> > open
> > for at least 72 hours ***
> >
> > Note that we are voting upon the source (tag), binaries are provided for
> > convenience.
> >
> > Source and binary files:
> > https://dist.apache.org/repos/dist/dev/incubator/pulsar/
> > pulsar-2.0.0-rc1-incubating-candidate-4/
> >
> > SHA-1 checksums:
> > a959a33500508d0ba690ca177eb39cf83dddf022
> > apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz
> > 5b9bedd2f284c5a8d95ba6dc3c70af8c266fbb3b
> > apache-pulsar-2.0.0-rc1-incubating-src.tar.gz
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachepulsar-1014/
> >
> > The tag to be voted upon:
> > v2.0.0-rc1-incubating-candidate-4 (e5d3bda9607703c2e012983c7ef64f
> > 5eb4118de7)
> > https://github.com/apache/incubator-pulsar/releases/tag/
> > v2.0.0-rc1-incubating-candidate-4
> >
> > Pulsar's KEYS file containing PGP keys we use to sign the release:
> > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
> >
> > Please download the the source package, and follow the README to build
> > and run the Pulsar standalone service.
> > --
> > Matteo Merli
> > 
> >
>
-- 
Matteo Merli

[CANCELED] [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 4

[Matteo Merli]

On Sun, May 20, 2018 at 5:32 PM Matteo Merli  wrote:

> Willem, thanks for catching these issues.
>
> I have fixed the missing dependencies, specified the exact version of each
> of them
> and added a script to validate that new changes won't break it later.
> https://github.com/apache/incubator-pulsar/pull/1820
>
> I will cancel this vote and create a new candidate.
>
> Matteo
>
> On Sat, May 19, 2018 at 11:12 PM Willem Jiang 
> wrote:
>
>> Hi,
>>
>> As there are some License issues in the binary distribution (please check
>> the section4 for more information), I had to vote  -1 (binding).
>>
>> Here are the verifications which I did
>> 1. check the checksums and verify the KEY.
>>   These KEY are not signed by the others, so I got the warning WARNING:
>> This key is not certified with a trusted signature!
>>
>> 2. Checked the License and Notice file of the source distribution.
>>   It looks good.
>>
>> 3. Built the source with instruction of README and start the server
>>   It works and I can start the standalone server.
>>   I also checked the distribution file in the all directory, I can get the
>> binary and source distribution there.
>>
>> 4. Checked the License and Notice file of the binary distribution.
>> There is not version of bundled jars specified in the License file. It
>> could cause some trouble as the License could be changed in different
>> versions of jar distribution.
>>
>>  Most of the bundled jars are specified in the License file, but some of
>> them are missed.
>>
>> * com.google.errorprone-error_prone_annotations-2.0.19.jar
>>
>> * com.google.instrumentation-instrumentation-api-0.4.3.jar
>>
>> * com.squareup.okhttp-okhttp-2.5.0.jar
>>
>> * com.squareup.okio-okio-1.6.0.jar
>>
>> * org.apache.distributedlog-distributedlog-core-shaded-4.7.0.jar
>>
>> The javassist jar is not CDDL license, it has multiple licenses
>> ASL,LGPL,MPL (we need to pick one of them).
>>
>> * org.javassist-javassist-3.21.0-GA.jar
>>
>>
>> Willem Jiang
>>
>>
>> On Fri, May 18, 2018 at 11:35 AM, Matteo Merli  wrote:
>>
>> > This is the fourth release candidate for Apache Pulsar, version
>> > 2.0.0-rc1-incubating.
>> >
>> > Pulsar is a highly scalable, low latency messaging platform running on
>> > commodity hardware.
>> > It provides simple pub-sub semantics over topics, guaranteed
>> at-least-once
>> > delivery of
>> > messages, automatic cursor management for subscribers, and
>> geo-replication.
>> >
>> > Link to the voting thread on pulsar dev list:
>> > https://lists.apache.org/thread.html/865ac7e993265a31512642c5f29e53
>> > e65f4199b931a5ae91d07fba77@%3Cdev.pulsar.apache.org%3E
>> >
>> > It fixes the following issues:
>> > https://github.com/apache/incubator-pulsar/milestone/12?closed=1
>> >
>> > *** Please download, test and vote on this release. This vote will stay
>> > open
>> > for at least 72 hours ***
>> >
>> > Note that we are voting upon the source (tag), binaries are provided for
>> > convenience.
>> >
>> > Source and binary files:
>> > https://dist.apache.org/repos/dist/dev/incubator/pulsar/
>> > pulsar-2.0.0-rc1-incubating-candidate-4/
>> >
>> > SHA-1 checksums:
>> > a959a33500508d0ba690ca177eb39cf83dddf022
>> > apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz
>> > 5b9bedd2f284c5a8d95ba6dc3c70af8c266fbb3b
>> > apache-pulsar-2.0.0-rc1-incubating-src.tar.gz
>> >
>> > Maven staging repo:
>> >
>> https://repository.apache.org/content/repositories/orgapachepulsar-1014/
>> >
>> > The tag to be voted upon:
>> > v2.0.0-rc1-incubating-candidate-4 (e5d3bda9607703c2e012983c7ef64f
>> > 5eb4118de7)
>> > https://github.com/apache/incubator-pulsar/releases/tag/
>> > v2.0.0-rc1-incubating-candidate-4
>> >
>> > Pulsar's KEYS file containing PGP keys we use to sign the release:
>> > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
>> >
>> > Please download the the source package, and follow the README to build
>> > and run the Pulsar standalone service.
>> > --
>> > Matteo Merli
>> > 
>> >
>>
> --
> Matteo Merli
> 
>
-- 
Matteo Merli

[VOTE] Release Apache NetBeans 9.0 RC1 (incubating) rc1

[Emilian Bold]

Hi all,

The Apache NetBeans community has voted on and approved a proposal to release 
Apache NetBeans 9.0 RC1 (incubating) rc1.

We now kindly request that the Incubator PMC members review and vote on this 
incubator release candidate.

Apache NetBeans 9.0 RC1 (incubating) vote thread:

https://lists.apache.org/thread.html/c2a06adc83e2819e6d96c7dff8d0e22a97001f99bfda12515d4d9609@%3Cdev.netbeans.apache.org%3E

Apache NetBeans 9.0 RC1 (incubating) vote result thread:

https://lists.apache.org/thread.html/94f7a5e4601e26c7edb8264df7df53dd8ed215ecfc568816a162f2af@%3Cdev.netbeans.apache.org%3E

Apache NetBeans 9.0 RC1 (incubating) constitutes all the modules in the Apache 
NetBeans Git repo, which together provide the NetBeans Platform (i.e., the 
underlying application framework), as well as all the modules that provide the 
Java SE-related features of Apache NetBeans.
In short, Apache NetBeans 9.0 RC1 (incubating) is a full IDE for Java SE 
development.

Build artifacts available here:

https://dist.apache.org/repos/dist/dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-rc1-rc1

The specific artifact to be voted on:

https://dist.apache.org/repos/dist/dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-rc1-rc1/incubating-netbeans-java-9.0-rc1-source.zip

Included in the above are the DEPENDENCIES, DISCLAIMER, LICENSE, and NOTICE 
files, as well as a README file with build instructions, which are the same as 
these:

https://github.com/apache/incubator-netbeans/blob/master/README.md

SHA1: a1a265455c8246f849b14982fa3c36b351b21876

KEYS file:

https://dist.apache.org/repos/dist/release/incubator/netbeans/KEYS

Apache NetBeans Git Repo tag: 9.0-rc1-rc1:

https://github.com/apache/incubator-netbeans/tree/9.0-rc1-rc1

Note: NetBeans license violation checks are managed via the rat-exclusions.txt 
file:

https://github.com/apache/incubator-netbeans/blob/master/nbbuild/rat-exclusions.txt

Rat report shows no unknown licenses, except for license files:

https://builds.apache.org/job/incubator-netbeans-release/302/artifact/rat-java-temp/nbbuild/build/rat-report.txt

The license files listed in the Rat report are known and an issue exists for 
solving this:

https://issues.apache.org/jira/browse/NETBEANS-305

Included as a convenience binary, not relevant for the voting purposes (unzip 
it, run it and you'll see Apache NetBeans):

https://dist.apache.org/repos/dist/dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-rc1-rc1/incubating-netbeans-java-9.0-rc1-bin.zip

Also included as a convenience binary the NBMs:

https://dist.apache.org/repos/dist/dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-rc1-rc1/nbms

New & Noteworthy features of the 9.0 Release:

https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+New+and+Noteworthy

Release specific wiki page:

https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+RC1

How (and what) to try out the release:

1. Download the artifact to be voted on and unzip it.
2. Build it using the README provided by the artifact.
3. Look in nbbuild/netbeans for the NetBeans installation created by the build 
process.
4. Run the NetBeans executable and (if you're running on JDK 8) you'll be 
prompted to install nb-javac, after agreeing to its licensing terms, and (if 
you're running on JDK 9), you'll be able to use javac directly from JDK 9 and, 
optionally, you'll be prompted to install nb-javac, after agreeing to its 
licensing terms.

If the above succeeds, i.e., Apache NetBeans installs and starts up, you will 
have a development environment that complies with Apache IP requirements and 
you should vote +1 in this thread.

Please try out the package, using the instructions above, and vote!

The vote is open for 7 days

[ ] +1 Release this package as Apache NetBeans 9.0 RC1 (incubating)
[ ] 0 I don't feel strongly about it, but I'm okay with the release
[ ] -1 Do not release this package because...


Emilian Bold
on behalf of the Apache NetBeans PPMC

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache ECharts (incubating) 4.1.0.rc3

[Justin Mclean]

Hi,

Releases at the ASF must not contain compiled code. You can if you want
also produce a conviance binary for users at the same time but the source
release needs to contain no compiled code otherwise it's not open source.

Thanks,
Justin

On Mon., 21 May 2018, 7:10 am SHUANG SU,  wrote:

> Thanks, Willem.
>
> But I will explain the reason that provides an all-in-one artifact.
>
> I understand that one of the reasons for separating src and binary files
> is that in some project the compilation is depending on the target runtime
> environment and thus the products cannot be enumerated completely.
> The other reason might be that the binary files are different to be
> checked.
> (Am I correct? or miss something notable?)
>
> But in this kind of JavaScript program, the built products is environment
> independent and can be enumerated completely.
>
> And the build products of the JavaScript project is text-based, which can
> be
> checked basically.
>
> Moreover, there are too many approaches to require and use a JavaScript
> project.
> First of all, a user project may be a browser project or run on
> a server (Node.js) or both.
> Both in those runtime environments, the user project may need to required a
> pre-combined
> built file via AMD or CommonJS module loader or global variable or some
> bundle tools like
> Webpack and rollup.js (provided in dist/**).
> Or the user project may intent to require files separately on demand via
> CommonJS
> or some bundle tools like Webpack and rollup.js (provided in lib/**).
> Or the user project may intent to require files via ES module loader
> (provided in src/**).
> During the development of user projects, probably more than one approaches
> are needed.
>
> So we both provide those files all-in-one in the artifacts for the
> convenience of the users.
> And this way follows the convention of most of the JavaSript libs, and it
> works well for years in
> the ECharts community.
>
>
> Truly,
> Su Shuang
>
>
>
> --
>  Su Shuang (100pah)
> --
>
>
> 2018-05-21 0:25 GMT+08:00 Kevin A. McGrail :
>
> > If the release candidate isn't correct for the artifacts you need to roll
> > an rc4 which might be two files not one and send that for a vote.
> >
> > On Sat, May 19, 2018, 22:34 Willem Jiang  wrote:
> >
> > > Hi,
> > >
> > > As there is only one zip file, I guess it just the src distribution.
> > > But after went through the file, I found lot of echart js files in the
> > dist
> > > directory and the rat jar.
> > >
> > > So I'm confused what's the purpose of apache-echarts-4.1.0.rc3-
> > > incubating.zip
> > >
> > > Normally we distribute the src and binary files separately.
> > >
> > >
> > >
> > > Willem Jiang
> > >
> > > Blog: http://willemjiang.blogspot.com (English)
> > >   http://jnn.iteye.com  (Chinese)
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > On Thu, May 17, 2018 at 7:42 PM, SHUANG SU 
> > wrote:
> > >
> > > > I am pleased to be calling this vote for the release of Apache
> ECharts
> > > > 4.1.0.rc3.
> > > >
> > > > Apache ECharts community has voted and approved the release.
> > > >
> > > > Vote thread:
> > > > https://lists.apache.org/thread.html/67dffef28ecffd66689ac991ca027c
> > > > 0868d734629949d958e7b12dd3@%3Cdev.echarts.apache.org%3E
> > > >
> > > > Results thread:
> > > > https://lists.apache.org/thread.html/3a6e627a7e07d5de0856296d44bb40
> > > > 8e17ee6795cc74ef190a7a5d23@%3Cdev.echarts.apache.org%3E
> > > >
> > > > The release candidate to be voted over is available at:
> > > > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.1.0.rc3/
> > > >
> > > > The release candidate is signed with a GPG key available at:
> > > > https://dist.apache.org/repos/dist/dev/incubator/echarts/KEYS
> > > >
> > > > A tagged git repository is available for review at:
> > > > https://github.com/apache/incubator-echarts/releases/tag/4.1.0.rc3
> > > >
> > > > The Git commit for this release is:
> > > > https://gitbox.apache.org/repos/asf?p=incubator-echarts.
> > > > git;a=commit;h=f98eb21
> > > >
> > > > The Release Note is available in:
> > > > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.
> > > > 1.0.rc3/RELEASE_NOTE.txt
> > > >
> > > > Some shell commands for validating the release:
> > > >
> > > > ```shell
> > > > # Download the release:
> > > > curl
> > > > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.
> > > > 1.0.rc3/apache-echarts-4.1.0.rc3-incubating.zip
> > > > -o apache-echarts-4.1.0.rc3-incubating.zip
> > > > unzip apache-echarts-4.1.0.rc3-incubating.zip -d
> > > > apache-echarts-4.1.0.rc3-incubating > /dev/null
> > > >
> > > > # Rebuild the project:
> > > > cd "apache-echarts-4.1.0.rc3-incubating" && npm install && cd ..
> > > > node "apache-echarts-4.1.0.rc3-incubating/build/build.js" --release
> > > > # (See help: `node "apache-echarts-4.1.0.rc3-
> > 

Re: [VOTE] Release Apache ECharts (incubating) 4.1.0.rc3

[SHUANG SU]

Thanks, Willem.

But I will explain the reason that provides an all-in-one artifact.

I understand that one of the reasons for separating src and binary files
is that in some project the compilation is depending on the target runtime
environment and thus the products cannot be enumerated completely.
The other reason might be that the binary files are different to be checked.
(Am I correct? or miss something notable?)

But in this kind of JavaScript program, the built products is environment
independent and can be enumerated completely.

And the build products of the JavaScript project is text-based, which can
be
checked basically.

Moreover, there are too many approaches to require and use a JavaScript
project.
First of all, a user project may be a browser project or run on
a server (Node.js) or both.
Both in those runtime environments, the user project may need to required a
pre-combined
built file via AMD or CommonJS module loader or global variable or some
bundle tools like
Webpack and rollup.js (provided in dist/**).
Or the user project may intent to require files separately on demand via
CommonJS
or some bundle tools like Webpack and rollup.js (provided in lib/**).
Or the user project may intent to require files via ES module loader
(provided in src/**).
During the development of user projects, probably more than one approaches
are needed.

So we both provide those files all-in-one in the artifacts for the
convenience of the users.
And this way follows the convention of most of the JavaSript libs, and it
works well for years in
the ECharts community.


Truly,
Su Shuang



--
 Su Shuang (100pah)
--


2018-05-21 0:25 GMT+08:00 Kevin A. McGrail :

> If the release candidate isn't correct for the artifacts you need to roll
> an rc4 which might be two files not one and send that for a vote.
>
> On Sat, May 19, 2018, 22:34 Willem Jiang  wrote:
>
> > Hi,
> >
> > As there is only one zip file, I guess it just the src distribution.
> > But after went through the file, I found lot of echart js files in the
> dist
> > directory and the rat jar.
> >
> > So I'm confused what's the purpose of apache-echarts-4.1.0.rc3-
> > incubating.zip
> >
> > Normally we distribute the src and binary files separately.
> >
> >
> >
> > Willem Jiang
> >
> > Blog: http://willemjiang.blogspot.com (English)
> >   http://jnn.iteye.com  (Chinese)
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Thu, May 17, 2018 at 7:42 PM, SHUANG SU 
> wrote:
> >
> > > I am pleased to be calling this vote for the release of Apache ECharts
> > > 4.1.0.rc3.
> > >
> > > Apache ECharts community has voted and approved the release.
> > >
> > > Vote thread:
> > > https://lists.apache.org/thread.html/67dffef28ecffd66689ac991ca027c
> > > 0868d734629949d958e7b12dd3@%3Cdev.echarts.apache.org%3E
> > >
> > > Results thread:
> > > https://lists.apache.org/thread.html/3a6e627a7e07d5de0856296d44bb40
> > > 8e17ee6795cc74ef190a7a5d23@%3Cdev.echarts.apache.org%3E
> > >
> > > The release candidate to be voted over is available at:
> > > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.1.0.rc3/
> > >
> > > The release candidate is signed with a GPG key available at:
> > > https://dist.apache.org/repos/dist/dev/incubator/echarts/KEYS
> > >
> > > A tagged git repository is available for review at:
> > > https://github.com/apache/incubator-echarts/releases/tag/4.1.0.rc3
> > >
> > > The Git commit for this release is:
> > > https://gitbox.apache.org/repos/asf?p=incubator-echarts.
> > > git;a=commit;h=f98eb21
> > >
> > > The Release Note is available in:
> > > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.
> > > 1.0.rc3/RELEASE_NOTE.txt
> > >
> > > Some shell commands for validating the release:
> > >
> > > ```shell
> > > # Download the release:
> > > curl
> > > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.
> > > 1.0.rc3/apache-echarts-4.1.0.rc3-incubating.zip
> > > -o apache-echarts-4.1.0.rc3-incubating.zip
> > > unzip apache-echarts-4.1.0.rc3-incubating.zip -d
> > > apache-echarts-4.1.0.rc3-incubating > /dev/null
> > >
> > > # Rebuild the project:
> > > cd "apache-echarts-4.1.0.rc3-incubating" && npm install && cd ..
> > > node "apache-echarts-4.1.0.rc3-incubating/build/build.js" --release
> > > # (See help: `node "apache-echarts-4.1.0.rc3-
> incubating/build/build.js"
> > > --help`)
> > >
> > > # Run Apache Rat:
> > > java -jar "apache-echarts-4.1.0.rc3-incubating/build/rat/runrat.jar" |
> > > less
> > > # (See help: `java -jar
> > > "apache-echarts-4.1.0.rc3-incubating/build/rat/runrat.jar" --help`)
> > > ```
> > >
> > >
> > > Please vote on releasing this package as:
> > > Apache ECharts 4.1.0.rc3
> > >
> > > This vote will be open until "2018-05-20T12:33:24.955Z".
> > >
> > > [ ] +1 Release this package
> > > [ ] 0 I don't feel strongly about it, but don't object
> > > [ ] -1 Do not release this 

[VOTE] Retire the Slider podling

[Billie Rinaldi]

After a long period of low activity, the Slider PPMC has recently decided
upon retirement [1]. Please vote on whether we should retire the Slider
podling. Here is my +1 (binding).

[ ] +1 Retire Slider
[ ] +0 No opinion
[ ] -1 Do not retire Slider because ...

This vote will remain open for 72 hours.

[1]: https://s.apache.org/V8SB

Re: [VOTE] Release Apache ECharts (incubating) 4.1.0.rc3

[Kevin A. McGrail]

If the release candidate isn't correct for the artifacts you need to roll
an rc4 which might be two files not one and send that for a vote.

On Sat, May 19, 2018, 22:34 Willem Jiang  wrote:

> Hi,
>
> As there is only one zip file, I guess it just the src distribution.
> But after went through the file, I found lot of echart js files in the dist
> directory and the rat jar.
>
> So I'm confused what's the purpose of apache-echarts-4.1.0.rc3-
> incubating.zip
>
> Normally we distribute the src and binary files separately.
>
>
>
> Willem Jiang
>
> Blog: http://willemjiang.blogspot.com (English)
>   http://jnn.iteye.com  (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Thu, May 17, 2018 at 7:42 PM, SHUANG SU  wrote:
>
> > I am pleased to be calling this vote for the release of Apache ECharts
> > 4.1.0.rc3.
> >
> > Apache ECharts community has voted and approved the release.
> >
> > Vote thread:
> > https://lists.apache.org/thread.html/67dffef28ecffd66689ac991ca027c
> > 0868d734629949d958e7b12dd3@%3Cdev.echarts.apache.org%3E
> >
> > Results thread:
> > https://lists.apache.org/thread.html/3a6e627a7e07d5de0856296d44bb40
> > 8e17ee6795cc74ef190a7a5d23@%3Cdev.echarts.apache.org%3E
> >
> > The release candidate to be voted over is available at:
> > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.1.0.rc3/
> >
> > The release candidate is signed with a GPG key available at:
> > https://dist.apache.org/repos/dist/dev/incubator/echarts/KEYS
> >
> > A tagged git repository is available for review at:
> > https://github.com/apache/incubator-echarts/releases/tag/4.1.0.rc3
> >
> > The Git commit for this release is:
> > https://gitbox.apache.org/repos/asf?p=incubator-echarts.
> > git;a=commit;h=f98eb21
> >
> > The Release Note is available in:
> > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.
> > 1.0.rc3/RELEASE_NOTE.txt
> >
> > Some shell commands for validating the release:
> >
> > ```shell
> > # Download the release:
> > curl
> > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.
> > 1.0.rc3/apache-echarts-4.1.0.rc3-incubating.zip
> > -o apache-echarts-4.1.0.rc3-incubating.zip
> > unzip apache-echarts-4.1.0.rc3-incubating.zip -d
> > apache-echarts-4.1.0.rc3-incubating > /dev/null
> >
> > # Rebuild the project:
> > cd "apache-echarts-4.1.0.rc3-incubating" && npm install && cd ..
> > node "apache-echarts-4.1.0.rc3-incubating/build/build.js" --release
> > # (See help: `node "apache-echarts-4.1.0.rc3-incubating/build/build.js"
> > --help`)
> >
> > # Run Apache Rat:
> > java -jar "apache-echarts-4.1.0.rc3-incubating/build/rat/runrat.jar" |
> > less
> > # (See help: `java -jar
> > "apache-echarts-4.1.0.rc3-incubating/build/rat/runrat.jar" --help`)
> > ```
> >
> >
> > Please vote on releasing this package as:
> > Apache ECharts 4.1.0.rc3
> >
> > This vote will be open until "2018-05-20T12:33:24.955Z".
> >
> > [ ] +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.
> >
> >
> > --
> >  Su Shuang (100pah)
> > --
> >
>

Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-beta

[???? Sheng Wu]

Hi, IPMC 
I am asking the release vote, again. :)  Haven't had one yet. Hope we can have 
enough vote in 72 hours.


Thanks.



Sheng Wu
Apache SkyWalking

From Wu Sheng 's phone.

---Original---
From: ".??"<8082...@qq.com>
Date: Fri, May 18, 2018 10:06 AM
To: "general";
Subject: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-beta


Hi All,
This is a call for vote to release Apache SkyWalking (Incubating) version 
5.0.0-beta.


The Apache SkyWalking community has tested, voted and approved the proposed
release of Apache SkyWalking (Incubating) 5.0.0-beta


We now kindly request the Incubator PMC members review and vote on this
incubator release.


SkyWalking: APM (application performance monitor) tool for distributed systems, 
especially designed for microservices, cloud native and container-based 
(Docker, Kubernetes, Mesos) architectures. 
Underlying technology is a distributed tracing system.



Vote Thread:
https://lists.apache.org/thread.html/77df7fc536a95d2e3c4121a3f2faf61371c31a22f1678a9d45134904@%3Cdev.skywalking.apache.org%3E


Result Thread:
https://lists.apache.org/thread.html/ba0939023e7e856b79093be1f0b9e4e15520e5f5f67344260cb5c3ff@%3Cdev.skywalking.apache.org%3E


Release notes:
* https://github.com/apache/incubator-skywalking/blob/master/CHANGES.md#500-beta
Release Candidate:


*https://dist.apache.org/repos/dist/dev/incubator/skywalking/5.0.0-beta/


Maven 2 staging repository:
*https://repository.apache.org/content/repositories/orgapacheskywalking-1011/org/apache/skywalking/
 


Release Tag :
* v5.0.0-beta


Release CommitID :
* 5ddc4e714f2570421779a11f2589ffc32d2b8b21


Keys to verify the Release Candidate :
*  http://pgp.mit.edu:11371/pks/lookup?op=get=0x2EF5026E70A55777 
corresponding to pen...@apache.org


Guide to build the release from source :
* 
https://github.com/apache/incubator-skywalking/blob/master/docs/en/How-to-build.md


Voting will start now (May 18th, 2018) and will remain open for at least 72 
hours, Request all IPMC members to give their vote.
[ ] +1 Release this package.
[ ] +0 No opinion.
[ ] -1 Do not release this package because??.


??
Yongsheng Peng
Apache SkyWalking PPMC member

Re: scala/play community?

[Romain Manni-Bucau]

Seems there is no big enthusiasm - which is what i kind of expected ;),  so
I guess I'll keep it on github for now (https://github.com/rmannibucau/playx).
If anyone becomes interested and feels we can create a community, dont
hesitate to ping me.

Thanks guys.

Le jeu. 17 mai 2018 02:55, Willem Jiang  a écrit :

> As there are bunch of big data projects which use Scala @asf,
> I guess here are some of Scala developer could be interested to expose the
> big data service in an easy way.
>
>
>
>
>
> Willem Jiang
>
> Blog: http://willemjiang.blogspot.com (English)
>   http://jnn.iteye.com  (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Wed, May 16, 2018 at 11:27 PM, Matt Sicker  wrote:
>
> > I've been involved in Scala and Akka projects before, but not Play,
> though.
> >
> > On 16 May 2018 at 07:43, Jean-Baptiste Onofré  wrote:
> >
> > > Hi Romain,
> > >
> > > AFAIK, we don't have any project for now related to scala@play.
> > >
> > > Even if it sounds very interesting, I'm not sure a servlet/jaxrs bridge
> > > would be enough for a incubator project (especially in term of
> > community).
> > >
> > > Let's see feedback from the others.
> > >
> > > Regards
> > > JB
> > >
> > >
> > > On 16/05/2018 14:40, Romain Manni-Bucau wrote:
> > >
> > >> Hi guys,
> > >>
> > >> I wonder if we have some scala@play community or not @asf.
> > >>
> > >> I will likely try to bring a servlet/jaxrs bridge soon and wonder if
> > >> proposing it @asf can be interesting (otherwise I just put it on
> > github).
> > >>
> > >> Any inputs welcomed.
> > >>
> > >> Romain Manni-Bucau
> > >> @rmannibucau  |  Blog
> > >>  | Old Blog
> > >>  | Github <
> > >> https://github.com/rmannibucau> |
> > >> LinkedIn  | Book
> > >>  > >> high-performance>
> > >>
> > >>
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
> >
> > --
> > Matt Sicker 
> >
>

Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 4

[Willem Jiang]

Hi,

As there are some License issues in the binary distribution (please check
the section4 for more information), I had to vote  -1 (binding).

Here are the verifications which I did
1. check the checksums and verify the KEY.
  These KEY are not signed by the others, so I got the warning WARNING:
This key is not certified with a trusted signature!

2. Checked the License and Notice file of the source distribution.
  It looks good.

3. Built the source with instruction of README and start the server
  It works and I can start the standalone server.
  I also checked the distribution file in the all directory, I can get the
binary and source distribution there.

4. Checked the License and Notice file of the binary distribution.
There is not version of bundled jars specified in the License file. It
could cause some trouble as the License could be changed in different
versions of jar distribution.

 Most of the bundled jars are specified in the License file, but some of
them are missed.

* com.google.errorprone-error_prone_annotations-2.0.19.jar

* com.google.instrumentation-instrumentation-api-0.4.3.jar

* com.squareup.okhttp-okhttp-2.5.0.jar

* com.squareup.okio-okio-1.6.0.jar

* org.apache.distributedlog-distributedlog-core-shaded-4.7.0.jar

The javassist jar is not CDDL license, it has multiple licenses
ASL,LGPL,MPL (we need to pick one of them).

* org.javassist-javassist-3.21.0-GA.jar


Willem Jiang


On Fri, May 18, 2018 at 11:35 AM, Matteo Merli  wrote:

> This is the fourth release candidate for Apache Pulsar, version
> 2.0.0-rc1-incubating.
>
> Pulsar is a highly scalable, low latency messaging platform running on
> commodity hardware.
> It provides simple pub-sub semantics over topics, guaranteed at-least-once
> delivery of
> messages, automatic cursor management for subscribers, and geo-replication.
>
> Link to the voting thread on pulsar dev list:
> https://lists.apache.org/thread.html/865ac7e993265a31512642c5f29e53
> e65f4199b931a5ae91d07fba77@%3Cdev.pulsar.apache.org%3E
>
> It fixes the following issues:
> https://github.com/apache/incubator-pulsar/milestone/12?closed=1
>
> *** Please download, test and vote on this release. This vote will stay
> open
> for at least 72 hours ***
>
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
>
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/incubator/pulsar/
> pulsar-2.0.0-rc1-incubating-candidate-4/
>
> SHA-1 checksums:
> a959a33500508d0ba690ca177eb39cf83dddf022
> apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz
> 5b9bedd2f284c5a8d95ba6dc3c70af8c266fbb3b
> apache-pulsar-2.0.0-rc1-incubating-src.tar.gz
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1014/
>
> The tag to be voted upon:
> v2.0.0-rc1-incubating-candidate-4 (e5d3bda9607703c2e012983c7ef64f
> 5eb4118de7)
> https://github.com/apache/incubator-pulsar/releases/tag/
> v2.0.0-rc1-incubating-candidate-4
>
> Pulsar's KEYS file containing PGP keys we use to sign the release:
> https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
>
> Please download the the source package, and follow the README to build
> and run the Pulsar standalone service.
> --
> Matteo Merli
> 
>