Build failed in Jenkins: pulsar-master #454

2018-05-03 Thread Apache Jenkins Server
See Changes: [mmerli] Changed property to tenant in various helper messages and tests (#1726) -- [...truncated 3.18 MB...] [INFO] python-kazoo [INFO] 0 upgraded, 13 newly in

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

2018-05-03 Thread P. Taylor Goetz
My bad. I stand corrected. ;) Nice work, BTW. -Taylor > On May 3, 2018, at 7:17 PM, Matteo Merli wrote: > > I will, though it's not my first release ;) signature.asc Description: Message signed with OpenPGP

Jenkins build is unstable: pulsar-master #453

2018-05-03 Thread Apache Jenkins Server
See

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

2018-05-03 Thread Matteo Merli
This is the second 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 w

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

2018-05-03 Thread Matteo Merli
On Thu, May 3, 2018 at 3:21 PM P. Taylor Goetz wrote: > Hi Matteo, > > When you cancel a VOTE, you should replace the “Re:” in the subject line > with “[CANCELED]”. IIRC, there is some ASF tooling that looks for that. > Thanks, noted and replied. > > A few other things: > > - The release artif

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

2018-05-03 Thread Matteo Merli
On Thu, May 3, 2018 at 2:24 PM Matteo Merli wrote: > Closing this. I'm preparing candidate 2 > > > On Thu, May 3, 2018 at 12:37 PM Matteo Merli > wrote: > >> Good find. I will send a new release candidate with this fix in a few >> hours. In the meantime please still validate this candidate so th

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

2018-05-03 Thread P. Taylor Goetz
Hi Matteo, When you cancel a VOTE, you should replace the “Re:” in the subject line with “[CANCELED]”. IIRC, there is some ASF tooling that looks for that. A few other things: - The release artifacts should be prefixed with “apache-pulsar” - The checksum and signature files should be included

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

2018-05-03 Thread Matteo Merli
Closing this. I'm preparing candidate 2 On Thu, May 3, 2018 at 12:37 PM Matteo Merli wrote: > Good find. I will send a new release candidate with this fix in a few > hours. In the meantime please still validate this candidate so that we can > spot issues before "candidate 2" > > Matteo > > On Th

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

2018-05-03 Thread Matteo Merli
Good find. I will send a new release candidate with this fix in a few hours. In the meantime please still validate this candidate so that we can spot issues before "candidate 2" Matteo On Thu, May 3, 2018 at 12:23 PM Sijie Guo wrote: > Sorry. I have to put -1 here. > > source/binary distributio

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

2018-05-03 Thread Sijie Guo
Sorry. I have to put -1 here. source/binary distributions looks good (asc, sha1, sha512). pub/sub functionalities are good on both src and binary distribution, verified via standalone, pulsar-client and pulsar-perf release tag, artifacts are good as well. however I think functions is broken with

Build failed in Jenkins: pulsar-master #452

2018-05-03 Thread Apache Jenkins Server
See Changes: [github] Fixed authentication flow via Pulsar Proxy (#1707) [guosijie] PIP-17: provide DataBlockHeader and implementation (#1669) [guosijie] PIP-17: provide BlockAwareSegmentInputStream implementation

Slack digest for #dev - 2018-05-03

2018-05-03 Thread Apache Pulsar Slack
2018-05-02 18:18:33 UTC - Sijie Guo: the first RC of 2.0 is out, please help check and vote it - 2018-05-02 20:35:05 UTC - Jai Asher: Starting patc