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

[Sijie Guo]

On Mon, May 14, 2018 at 11:16 AM, Dave Fisher  wrote:

> Hi -
>
> > On May 14, 2018, at 10:57 AM, Sijie Guo  wrote:
> >
> > On Sun, May 13, 2018 at 7:49 PM, Matt Sicker  wrote:
> >
> >> On 13 May 2018 at 12:10, Matteo Merli  wrote:
> >>
> >>> The code in question is testing a feature that takes Jars from a user
> and
> >>> execute the code contained. Indeed the Jar should not be in the
> sources,
> >>> though I believe the test is correct here: we need to validate the
> >> specific
> >>> feature by dynamically loading a Jar.
> >>>
> >>
> >> By generating the binary jar from source files at test time, you'd avoid
> >> bundling any binary output files.
> >>
> >
> > I made the original change long time back in pulsar-functions for testing
> > submitting user-defined function. When we first contribute
> pulsar-functions
> > to pulsar, we probably didn't clean that up.
> > The intention behind that change is not including any source code or jar
> in
> > the test dependency tree. As including source code would make the testing
> > function as part of the test dependency, it would volatile the purpose of
> > testing submitting a user defined function. In this case,
> > "multifunction.jar" is the a "user-defined" function as the test
> resource.
>
> To be succinct The ASF produces open source software and including a
> pre-compiled binary in the release means that the project fails the open
> source definition. [1]
>
> It really doesn’t matter how or why. You will need to provide the source
> (as simple as it might be) and the maven configuration to build that
> trivial jar.
>

Okay. So if we provide the source file of that jar, is it allowed to
include a pre-compiled binary as test resources?



>
> Regards,
> Dave
>
> [1] https://opensource.org/osd
>
> >
> >
> >
> >
> >
> >>
> >>
>  (e.g., injecting a
> >>> module-info.class file at build time rather than requiring Java 9+ to
> >> build
> >>> regardless).
> >>>
> >>> I don't see any place in the code where we are using
> "module-info.class"
> >>> and the project requires Java 8 and not 9.
> >>>
> >>
> >> Sorry for the confusion, that was just an example from a problem I've
> seen
> >> before in another project.
> >>
> >> --
> >> Matt Sicker 
> >>
>
>

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

[Dave Fisher]

Hi -

> On May 14, 2018, at 10:57 AM, Sijie Guo  wrote:
> 
> On Sun, May 13, 2018 at 7:49 PM, Matt Sicker  wrote:
> 
>> On 13 May 2018 at 12:10, Matteo Merli  wrote:
>> 
>>> The code in question is testing a feature that takes Jars from a user and
>>> execute the code contained. Indeed the Jar should not be in the sources,
>>> though I believe the test is correct here: we need to validate the
>> specific
>>> feature by dynamically loading a Jar.
>>> 
>> 
>> By generating the binary jar from source files at test time, you'd avoid
>> bundling any binary output files.
>> 
> 
> I made the original change long time back in pulsar-functions for testing
> submitting user-defined function. When we first contribute pulsar-functions
> to pulsar, we probably didn't clean that up.
> The intention behind that change is not including any source code or jar in
> the test dependency tree. As including source code would make the testing
> function as part of the test dependency, it would volatile the purpose of
> testing submitting a user defined function. In this case,
> "multifunction.jar" is the a "user-defined" function as the test resource.

To be succinct The ASF produces open source software and including a 
pre-compiled binary in the release means that the project fails the open source 
definition. [1]

It really doesn’t matter how or why. You will need to provide the source (as 
simple as it might be) and the maven configuration to build that trivial jar.

Regards,
Dave

[1] https://opensource.org/osd

> 
> 
> 
> 
> 
>> 
>> 
 (e.g., injecting a
>>> module-info.class file at build time rather than requiring Java 9+ to
>> build
>>> regardless).
>>> 
>>> I don't see any place in the code where we are using "module-info.class"
>>> and the project requires Java 8 and not 9.
>>> 
>> 
>> Sorry for the confusion, that was just an example from a problem I've seen
>> before in another project.
>> 
>> --
>> Matt Sicker 
>> 



signature.asc
Description: Message signed with OpenPGP

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

[Matteo Merli]

Canceling this vote thread to remove pre-packaged jar used in unit tests.

Matteo

On Sat, May 12, 2018 at 7:18 PM Dave Fisher  wrote:

> Hi Pulsar Devs,
>
> Thanks Justin! I know that Pulsar Functions are new.
>
> $ jar tvf
> apache-pulsar-2.0.0-rc1-incubating/pulsar-functions/utils/src/test/resources/multifunction.jar
>  0 Wed Dec 13 01:00:28 PST 2017 META-INF/
>147 Wed Dec 13 01:00:28 PST 2017 META-INF/MANIFEST.MF
>  0 Wed Dec 13 00:58:36 PST 2017 org/
>  0 Wed Dec 13 00:58:36 PST 2017 org/apache/
>  0 Wed Dec 13 00:58:36 PST 2017 org/apache/pulsar/
>  0 Wed Dec 13 00:58:36 PST 2017 org/apache/pulsar/functions/
>  0 Wed Dec 13 00:58:36 PST 2017 org/apache/pulsar/functions/runtime/
>  0 Wed Dec 13 00:58:56 PST 2017
> org/apache/pulsar/functions/runtime/functioncache/
>683 Wed Dec 13 00:57:10 PST 2017
> org/apache/pulsar/functions/runtime/functioncache/AddFunction.class
>
> AddFunction is nowhere in the source. This is something that must be
> corrected.
>
> Sorry, but I am going to change my votes to +0 until there is an
> explanation. One option would be to remove this test …
>
> Please keep the eye out for jars and tars in the source.
>
> Regards,
> Dave
>
> On May 12, 2018, at 3:52 PM, Justin Mclean 
> wrote:
>
> Hi,
>
> Sorry but it’s -1 binding due to compiled code in source release.
>
> Frankly I’m surprised to see so many +1s with this obvious issue.
>
> I checked:
> - incubating in name
> - signatures and hashes correct
> - DISCLAIMER exists
> - LICENSE and NOTICE good
> - Unexpected jar in source release [1]
> - All source files have headers
>
> Thanks,
> Justin
>
>
> 1.  pulsar-functions/utils/src/test/resources/multifunction.jar
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>
> --
Matteo Merli

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

[Matteo Merli]

Hi Matt,

can you expand a bit more on the issue, because I'm not 100% sure I
understand it correctly.

> -1 as well. For strange build requirements that need to inject class
files,
that would still only be applied to the binary artifacts

The code in question is testing a feature that takes Jars from a user and
execute the code contained. Indeed the Jar should not be in the sources,
though I believe the test is correct here: we need to validate the specific
feature by dynamically loading a Jar.

> (e.g., injecting a
module-info.class file at build time rather than requiring Java 9+ to build
regardless).

I don't see any place in the code where we are using "module-info.class"
and the project requires Java 8 and not 9.

Thanks,
Matteo

On Sun, May 13, 2018 at 8:46 AM Matt Sicker  wrote:

> -1 as well. For strange build requirements that need to inject class files,
> that would still only be applied to the binary artifacts (e.g., injecting a
> module-info.class file at build time rather than requiring Java 9+ to build
> regardless).
>
> On 12 May 2018 at 21:17, Dave Fisher  wrote:
>
> > Hi Pulsar Devs,
> >
> > Thanks Justin! I know that Pulsar Functions are new.
> >
> > $ jar tvf apache-pulsar-2.0.0-rc1-incubating/pulsar-functions/
> > utils/src/test/resources/multifunction.jar
> >  0 Wed Dec 13 01:00:28 PST 2017 META-INF/
> >147 Wed Dec 13 01:00:28 PST 2017 META-INF/MANIFEST.MF
> >  0 Wed Dec 13 00:58:36 PST 2017 org/
> >  0 Wed Dec 13 00:58:36 PST 2017 org/apache/
> >  0 Wed Dec 13 00:58:36 PST 2017 org/apache/pulsar/
> >  0 Wed Dec 13 00:58:36 PST 2017 org/apache/pulsar/functions/
> >  0 Wed Dec 13 00:58:36 PST 2017 org/apache/pulsar/functions/runtime/
> >  0 Wed Dec 13 00:58:56 PST 2017 org/apache/pulsar/functions/
> > runtime/functioncache/
> >683 Wed Dec 13 00:57:10 PST 2017 org/apache/pulsar/functions/
> > runtime/functioncache/AddFunction.class
> >
> > AddFunction is nowhere in the source. This is something that must be
> > corrected.
> >
> > Sorry, but I am going to change my votes to +0 until there is an
> > explanation. One option would be to remove this test …
> >
> > Please keep the eye out for jars and tars in the source.
> >
> > Regards,
> > Dave
> >
> > On May 12, 2018, at 3:52 PM, Justin Mclean 
> > wrote:
> >
> > Hi,
> >
> > Sorry but it’s -1 binding due to compiled code in source release.
> >
> > Frankly I’m surprised to see so many +1s with this obvious issue.
> >
> > I checked:
> > - incubating in name
> > - signatures and hashes correct
> > - DISCLAIMER exists
> > - LICENSE and NOTICE good
> > - Unexpected jar in source release [1]
> > - All source files have headers
> >
> > Thanks,
> > Justin
> >
> >
> > 1.  pulsar-functions/utils/src/test/resources/multifunction.jar
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
> >
>
>
> --
> Matt Sicker 
>
-- 
Matteo Merli

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

[Matt Sicker]

-1 as well. For strange build requirements that need to inject class files,
that would still only be applied to the binary artifacts (e.g., injecting a
module-info.class file at build time rather than requiring Java 9+ to build
regardless).

On 12 May 2018 at 21:17, Dave Fisher  wrote:

> Hi Pulsar Devs,
>
> Thanks Justin! I know that Pulsar Functions are new.
>
> $ jar tvf apache-pulsar-2.0.0-rc1-incubating/pulsar-functions/
> utils/src/test/resources/multifunction.jar
>  0 Wed Dec 13 01:00:28 PST 2017 META-INF/
>147 Wed Dec 13 01:00:28 PST 2017 META-INF/MANIFEST.MF
>  0 Wed Dec 13 00:58:36 PST 2017 org/
>  0 Wed Dec 13 00:58:36 PST 2017 org/apache/
>  0 Wed Dec 13 00:58:36 PST 2017 org/apache/pulsar/
>  0 Wed Dec 13 00:58:36 PST 2017 org/apache/pulsar/functions/
>  0 Wed Dec 13 00:58:36 PST 2017 org/apache/pulsar/functions/runtime/
>  0 Wed Dec 13 00:58:56 PST 2017 org/apache/pulsar/functions/
> runtime/functioncache/
>683 Wed Dec 13 00:57:10 PST 2017 org/apache/pulsar/functions/
> runtime/functioncache/AddFunction.class
>
> AddFunction is nowhere in the source. This is something that must be
> corrected.
>
> Sorry, but I am going to change my votes to +0 until there is an
> explanation. One option would be to remove this test …
>
> Please keep the eye out for jars and tars in the source.
>
> Regards,
> Dave
>
> On May 12, 2018, at 3:52 PM, Justin Mclean 
> wrote:
>
> Hi,
>
> Sorry but it’s -1 binding due to compiled code in source release.
>
> Frankly I’m surprised to see so many +1s with this obvious issue.
>
> I checked:
> - incubating in name
> - signatures and hashes correct
> - DISCLAIMER exists
> - LICENSE and NOTICE good
> - Unexpected jar in source release [1]
> - All source files have headers
>
> Thanks,
> Justin
>
>
> 1.  pulsar-functions/utils/src/test/resources/multifunction.jar
> -
> 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 3

[Dave Fisher]

Hi Pulsar Devs,

Thanks Justin! I know that Pulsar Functions are new.

$ jar tvf 
apache-pulsar-2.0.0-rc1-incubating/pulsar-functions/utils/src/test/resources/multifunction.jar
 0 Wed Dec 13 01:00:28 PST 2017 META-INF/
   147 Wed Dec 13 01:00:28 PST 2017 META-INF/MANIFEST.MF
 0 Wed Dec 13 00:58:36 PST 2017 org/
 0 Wed Dec 13 00:58:36 PST 2017 org/apache/
 0 Wed Dec 13 00:58:36 PST 2017 org/apache/pulsar/
 0 Wed Dec 13 00:58:36 PST 2017 org/apache/pulsar/functions/
 0 Wed Dec 13 00:58:36 PST 2017 org/apache/pulsar/functions/runtime/
 0 Wed Dec 13 00:58:56 PST 2017 
org/apache/pulsar/functions/runtime/functioncache/
   683 Wed Dec 13 00:57:10 PST 2017 
org/apache/pulsar/functions/runtime/functioncache/AddFunction.class

AddFunction is nowhere in the source. This is something that must be corrected.

Sorry, but I am going to change my votes to +0 until there is an explanation. 
One option would be to remove this test …

Please keep the eye out for jars and tars in the source.

Regards,
Dave

> On May 12, 2018, at 3:52 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> Sorry but it’s -1 binding due to compiled code in source release.
> 
> Frankly I’m surprised to see so many +1s with this obvious issue.
> 
> I checked:
> - incubating in name
> - signatures and hashes correct
> - DISCLAIMER exists
> - LICENSE and NOTICE good
> - Unexpected jar in source release [1]
> - All source files have headers
> 
> Thanks,
> Justin
> 
> 
> 1.  pulsar-functions/utils/src/test/resources/multifunction.jar
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 



signature.asc
Description: Message signed with OpenPGP

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

[Dave Fisher]

+1 (binding)

Note that with Taylor, Jim and I this release has the 3 requisite IPMC +1 
Votes. You still need to present the VOTE thread to general@incubator in case 
any other IPMC member wishes to review.

Both Source and Binary:
Checked hashes and signatures
Check LICENSE, NOTICE, DISCLAIMER and README.
Builds
Built the source
Built w/tests failed in the Broker
<<< FAILURE! - in org.apache.pulsar.broker.loadbalance.LoadBalancerTest
java.lang.AssertionError: expected [true] but found [false]
<<< FAILURE! - in org.apache.pulsar.broker.service.ReplicatorGlobalNSTest
org.testng.internal.thread.ThreadTimeoutException: Method 
org.apache.pulsar.broker.service.ReplicatorGlobalNSTest.setup() didn't finish 
within the time-out 3
<<< FAILURE! - in org.apache.pulsar.broker.service.ReplicatorTest
org.testng.internal.thread.ThreadTimeoutException: Method 
org.apache.pulsar.broker.service.ReplicatorTest.setup() didn't finish within 
the time-out 3
<<< FAILURE! - in org.apache.pulsar.broker.service.v1.V1_ReplicatorTest
org.testng.internal.thread.ThreadTimeoutException: Method 
org.apache.pulsar.broker.service.v1.V1_ReplicatorTest.setup() didn't finish 
within the time-out 3
<<< FAILURE! - in org.apache.pulsar.broker.zookeeper.ZooKeeperClientAspectJTest
java.util.concurrent.TimeoutException
I’ll consider these to be issues with my setup.
RAT Check - passes.
mvn apache-rat:check

Regards,
Dave


> On May 8, 2018, at 3:22 PM, Matteo Merli  wrote:
> 
> This is the third release candidate for Apache Pulsar, version
> 2.0.0-rc1-incubating.
> 
> 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-3/
> 
> SHA-1 checksums:
> b1a392c5935448da195eb927520fe6deb20182fc
> apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz
> 8c547a3e0afaee3446c770c076d5803e7e7da1c2
> apache-pulsar-2.0.0-rc1-incubating-src.tar.gz
> 
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1013/
> 
> The tag to be voted upon:
> v2.0.0-rc1-incubating-candidate-3 (9b33a8788f171f98528aeaa9040d16fc702404ef)
> https://github.com/apache/incubator-pulsar/releases/tag/v2.0.0-rc1-incubating-candidate-3
> 
> 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
> 



signature.asc
Description: Message signed with OpenPGP

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

[David Rusek]

+1 (non-binding)

On Wed, May 9, 2018 at 6:14 PM, Nozomi Kurihara <nkuri...@yahoo-corp.jp>
wrote:

> +1 (binding)
>
> Environment: MacOS 10.13.4
>
> * check sha1, sha512, asc
> * Bin distribution
> - start standalone
> - producer/consumer worked
> - pulsar-functions worked
> * Src distribution
> - compile and unit tests
> - RAT check
> - start standalone
> - producer/consumer worked
> - pulsar-functions worked
>
> Regards,
> Nozomi
>
> 
> 差出人: Rajan Dhabalia <rdhaba...@apache.org>
> 送信日時: 2018年5月10日 8:55:20
> 宛先: dev@pulsar.incubator.apache.org
> 件名: Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3
>
> +1 (binding)
>
> Environment: Mac-OS 10.12.6
>
> Checked:
>  - signatures and checksum
>  - maven repository artifacts
>  - start standalone service and client-test for producer/consumer (src/bin
> distribution)
>  - rat check on src distribution
>  - compile and unit test on src distribution
>
> Thanks,
> Rajan
>
> On Tue, May 8, 2018 at 3:22 PM, Matteo Merli <mme...@apache.org> wrote:
>
> > This is the third release candidate for Apache Pulsar, version
> > 2.0.0-rc1-incubating.
> >
> > 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-3/
> >
> > SHA-1 checksums:
> > b1a392c5935448da195eb927520fe6deb20182fc
> > apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz
> > 8c547a3e0afaee3446c770c076d5803e7e7da1c2
> > apache-pulsar-2.0.0-rc1-incubating-src.tar.gz
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachepulsar-1013/
> >
> > The tag to be voted upon:
> > v2.0.0-rc1-incubating-candidate-3 (9b33a8788f171f98528aeaa9040d16
> > fc702404ef)
> > https://github.com/apache/incubator-pulsar/releases/tag/
> > v2.0.0-rc1-incubating-candidate-3
> >
> > 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
> > <mme...@apache.org>
> >
>

RE: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3

[Nozomi Kurihara]

+1 (binding)

Environment: MacOS 10.13.4

* check sha1, sha512, asc
* Bin distribution
- start standalone
- producer/consumer worked
- pulsar-functions worked
* Src distribution
- compile and unit tests
- RAT check
- start standalone
- producer/consumer worked
- pulsar-functions worked

Regards,
Nozomi


差出人: Rajan Dhabalia <rdhaba...@apache.org>
送信日時: 2018年5月10日 8:55:20
宛先: dev@pulsar.incubator.apache.org
件名: Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3

+1 (binding)

Environment: Mac-OS 10.12.6

Checked:
 - signatures and checksum
 - maven repository artifacts
 - start standalone service and client-test for producer/consumer (src/bin
distribution)
 - rat check on src distribution
 - compile and unit test on src distribution

Thanks,
Rajan

On Tue, May 8, 2018 at 3:22 PM, Matteo Merli <mme...@apache.org> wrote:

> This is the third release candidate for Apache Pulsar, version
> 2.0.0-rc1-incubating.
>
> 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-3/
>
> SHA-1 checksums:
> b1a392c5935448da195eb927520fe6deb20182fc
> apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz
> 8c547a3e0afaee3446c770c076d5803e7e7da1c2
> apache-pulsar-2.0.0-rc1-incubating-src.tar.gz
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1013/
>
> The tag to be voted upon:
> v2.0.0-rc1-incubating-candidate-3 (9b33a8788f171f98528aeaa9040d16
> fc702404ef)
> https://github.com/apache/incubator-pulsar/releases/tag/
> v2.0.0-rc1-incubating-candidate-3
>
> 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
> <mme...@apache.org>
>

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

[Rajan Dhabalia]

+1 (binding)

Environment: Mac-OS 10.12.6

Checked:
 - signatures and checksum
 - maven repository artifacts
 - start standalone service and client-test for producer/consumer (src/bin
distribution)
 - rat check on src distribution
 - compile and unit test on src distribution

Thanks,
Rajan

On Tue, May 8, 2018 at 3:22 PM, Matteo Merli  wrote:

> This is the third release candidate for Apache Pulsar, version
> 2.0.0-rc1-incubating.
>
> 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-3/
>
> SHA-1 checksums:
> b1a392c5935448da195eb927520fe6deb20182fc
> apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz
> 8c547a3e0afaee3446c770c076d5803e7e7da1c2
> apache-pulsar-2.0.0-rc1-incubating-src.tar.gz
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1013/
>
> The tag to be voted upon:
> v2.0.0-rc1-incubating-candidate-3 (9b33a8788f171f98528aeaa9040d16
> fc702404ef)
> https://github.com/apache/incubator-pulsar/releases/tag/
> v2.0.0-rc1-incubating-candidate-3
>
> 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
> 
>

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

[P. Taylor Goetz]

+1 (binding)

-Taylor

> On May 8, 2018, at 6:22 PM, Matteo Merli  wrote:
> 
> This is the third release candidate for Apache Pulsar, version
> 2.0.0-rc1-incubating.
> 
> 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-3/
> 
> SHA-1 checksums:
> b1a392c5935448da195eb927520fe6deb20182fc
> apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz
> 8c547a3e0afaee3446c770c076d5803e7e7da1c2
> apache-pulsar-2.0.0-rc1-incubating-src.tar.gz
> 
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1013/
> 
> The tag to be voted upon:
> v2.0.0-rc1-incubating-candidate-3 (9b33a8788f171f98528aeaa9040d16fc702404ef)
> https://github.com/apache/incubator-pulsar/releases/tag/v2.0.0-rc1-incubating-candidate-3
> 
> 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
> 



signature.asc
Description: Message signed with OpenPGP

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

[Jim Jagielski]

+1 (binding)

> On May 8, 2018, at 6:22 PM, Matteo Merli  wrote:
> 
> This is the third release candidate for Apache Pulsar, version
> 2.0.0-rc1-incubating.
> 
> 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-3/
> 
> SHA-1 checksums:
> b1a392c5935448da195eb927520fe6deb20182fc
> apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz
> 8c547a3e0afaee3446c770c076d5803e7e7da1c2
> apache-pulsar-2.0.0-rc1-incubating-src.tar.gz
> 
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1013/
> 
> The tag to be voted upon:
> v2.0.0-rc1-incubating-candidate-3 (9b33a8788f171f98528aeaa9040d16fc702404ef)
> https://github.com/apache/incubator-pulsar/releases/tag/v2.0.0-rc1-incubating-candidate-3
> 
> 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
> 

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

[Jia Zhai]

+1 (non-binding)

Environment: macOS 10.13.2

* asc, sha1, sha512 are good for both src and binary distributions
* binary distribution
   - run standalone
   - be able to produce and consume messages
* src distribution
   - passed compile and all unit test.
   - run standalone with compiled binary, be able to produce and consume.



On Wed, May 9, 2018 at 9:11 AM, Sijie Guo  wrote:

> +1 (binding)
>
> Environment: macOS 10.13.1
>
> * asc, sha1, sha512 are good for both src and binary distributions
> * binary distribution
>- run standalone
>- be able to produce and consume messages
>- run perf
>- run functions
> * src distribution
>- be able to compile and run same set of tests on compiled binary
> * rat check is good
>
> - Sijie
>
> On Wed, May 9, 2018 at 6:22 AM, Matteo Merli  wrote:
>
> > This is the third release candidate for Apache Pulsar, version
> > 2.0.0-rc1-incubating.
> >
> > 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-3/
> >
> > SHA-1 checksums:
> > b1a392c5935448da195eb927520fe6deb20182fc
> > apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz
> > 8c547a3e0afaee3446c770c076d5803e7e7da1c2
> > apache-pulsar-2.0.0-rc1-incubating-src.tar.gz
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachepulsar-1013/
> >
> > The tag to be voted upon:
> > v2.0.0-rc1-incubating-candidate-3 (9b33a8788f171f98528aeaa9040d16
> > fc702404ef)
> > https://github.com/apache/incubator-pulsar/releases/tag/
> > v2.0.0-rc1-incubating-candidate-3
> >
> > 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
> > 
> >
>

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

[Sijie Guo]

+1 (binding)

Environment: macOS 10.13.1

* asc, sha1, sha512 are good for both src and binary distributions
* binary distribution
   - run standalone
   - be able to produce and consume messages
   - run perf
   - run functions
* src distribution
   - be able to compile and run same set of tests on compiled binary
* rat check is good

- Sijie

On Wed, May 9, 2018 at 6:22 AM, Matteo Merli  wrote:

> This is the third release candidate for Apache Pulsar, version
> 2.0.0-rc1-incubating.
>
> 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-3/
>
> SHA-1 checksums:
> b1a392c5935448da195eb927520fe6deb20182fc
> apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz
> 8c547a3e0afaee3446c770c076d5803e7e7da1c2
> apache-pulsar-2.0.0-rc1-incubating-src.tar.gz
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1013/
>
> The tag to be voted upon:
> v2.0.0-rc1-incubating-candidate-3 (9b33a8788f171f98528aeaa9040d16
> fc702404ef)
> https://github.com/apache/incubator-pulsar/releases/tag/
> v2.0.0-rc1-incubating-candidate-3
>
> 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
> 
>

[VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3

[Matteo Merli]

This is the third release candidate for Apache Pulsar, version
2.0.0-rc1-incubating.

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-3/

SHA-1 checksums:
b1a392c5935448da195eb927520fe6deb20182fc
apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz
8c547a3e0afaee3446c770c076d5803e7e7da1c2
apache-pulsar-2.0.0-rc1-incubating-src.tar.gz

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachepulsar-1013/

The tag to be voted upon:
v2.0.0-rc1-incubating-candidate-3 (9b33a8788f171f98528aeaa9040d16fc702404ef)
https://github.com/apache/incubator-pulsar/releases/tag/v2.0.0-rc1-incubating-candidate-3

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